Merge pull request #312 from softwarepub/release/0.9.0

Prepare for Release 0.9.0

Author: poikilotherm

CITATION.cff

@@ -14,7 +14,7 @@ title: hermes
 message: >-
   If you use this software, please cite it using the
   metadata from this file.
-version: 0.8.1
+version: 0.9.0
 license: "Apache-2.0"
 abstract: "Tool to automate software publication. Not stable yet."
 type: software

docs/source/dev/releasing.md

@@ -4,21 +4,25 @@
 
 To release a new version of HERMES when a new set of features and/or fixes have been merged, execute the following steps:
 
-1. Adjust the version number in `pyproject.toml` as necessary (major, minor or patch release).
-   Please create and merge a PR for this. Don't just push to `develop`.
-   To edit the version, you can use two ways:
+1. Adjust the version number in `pyproject.toml` and `CITATION.cff` as necessary (major, minor or patch release).
+   Please create a branch `release/v<version>` and merge it in a PR - don't just push to `develop`.
+   After merging, delete the "release" branch.
+   
+   To edit the version in `pyproject.toml`, there are two ways:
    - Manually edit the file with an editor.
    - Use `poetry version <rule>`. See also [Poetry Docs](https://python-poetry.org/docs/cli/#version)
+
 2. Create a pull request from `develop` to `main`.
 3. Check if all the CI pipelines for that PR succeed.
 3. Let the named maintainer (see GOVERNANCE.md) merge the PR into `main`.
 4. Create a new release [by using the Github UI](https://github.com/softwarepub/hermes/releases/new).
-   This also ensures usage of *annotated* tags to include releases in Software Heritage Archive.
    - Choose to create a new tag with the format `v<version number>`.
    - Target branch is `main`.
    - The release title will be set to the tag name, keep as is.
    - A description should be added, giving a very brief summary of the contained changes.
    - Publish the release.
+   
+   Note: this will also ensure usage of *annotated* tags, making Software Heritage archive the release.
 5. On `develop`, update the version in `pyproject.toml` to `<major>.<minor+1>.0.dev0` in another pull request.
    To edit the version, you can use two ways:
    - Manually edit the file with an editor.

pyproject.toml

@@ -9,7 +9,7 @@
 [tool.poetry]
 # Reference at https://python-poetry.org/docs/pyproject/
 name = "hermes"
-version = "0.9.0.dev0"
+version = "0.9.0"
 description = "Workflow to publish research software with rich metadata"
 homepage = "https://software-metadata.pub"
 license = "Apache-2.0"