version string; release instructions

Author: mvanbrab

README.md

@@ -28,7 +28,7 @@ Table of contents:
     * [Additional prerequisites](#additional-prerequisites)
     * [Testing the production version](#testing-the-production-version)
     * [Testing the development version](#testing-the-development-version)
-  * [Maintaining the version string](#maintaining-the-version-string)
+  * [Release activities](#release-activities)
 
 ## Preface
 
@@ -444,6 +444,6 @@ The procedure is the same as for testing the production version, except for step
    npm run dev-with-path
    ```
 
-### Maintaining the version string
+### Release activities
 
-Maintain the version string [here](./main/src/version.js) according to the rules in that file.
+See [RELEASE.md](./RELEASE.md).

RELEASE.md

@@ -0,0 +1,53 @@
+# Release activities
+
+* [Release tag](#release-tag)
+* [Finalize work on the development branch](#finalize-work-on-the-development-branch)
+* [Merge to the main branch](#merge-to-the-main-branch)
+* [Create a new release](#create-a-new-release)
+* [Back on the development branch](#back-on-the-development-branch)
+
+## Release tag
+
+Define the release tag. Example: `v1.7.0`.
+
+> Dut do not create the tag in git yet.
+
+## Finalize work on the development branch
+
+All feature branches and fix branches should be merged here
+and [CHANGELOG.md](./CHANGELOG.md) should reflect all modifications under the `## [Unreleased]` section.
+
+In [CHANGELOG.md](./CHANGELOG.md):
+
+* Create the new release section by adding a new release title line below the `## [Unreleased]` title line. Example: `## [1.7.0] - 2025-04-09`.
+* Add a new release link line near the end of the file. Example: `[1.7.0]: https://github.com/SolidLabResearch/generic-data-viewer-react-admin/releases/tag/v1.7.0`.
+* Update the `[Unreleased]` link in the bottom line to use the new release tag. Example: `[Unreleased]: https://github.com/SolidLabResearch/generic-data-viewer-react-admin/compare/v1.7.0...HEAD`
+
+Enter the release tag in the version string in [/main/src/version.js](./main/src/version.js).
+
+## Merge to the main branch
+
+Go to the github web interface.
+
+Make a pull request (example: `Merging for v1.7.0`) from the development branch to the main branch.
+
+Merge, without squashing (!).
+
+## Create a new release
+
+Still in the github web interface...
+
+Create the new release from the main branch.
+
+Enter the to be created new git tag here.
+
+In the release description, copy from [CHANGELOG.md](./CHANGELOG.md):
+
+* the new release section created above
+* the new release link created above
+
+Make sure to set the release as the latest release.
+
+## Back on the development branch
+
+Modify the version string in [/main/src/version.js](./main/src/version.js) back to `(unreleased)`.

main/src/version.js

@@ -1,5 +1,5 @@
 // Maintain the version string on the development branch:
 // - during development: set to (unreleased);
 // - right before merging to the main branch for making a new release: set to the new release tag (see https://github.com/SolidLabResearch/generic-data-viewer-react-admin/tags).
-const version = "(unreleased)";
+const version = "v1.7.0";
 export default version;