Skip to content

Commit

Permalink
Merge pull request #305 from tpvasconcelos/contrib
Browse files Browse the repository at this point in the history
Add link to GH compare
  • Loading branch information
tpvasconcelos authored Dec 24, 2024
2 parents 2fc16f2 + 396f34e commit 4dd703e
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/development/release_process.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ You need to have push-access to the project's repository to make releases. There
:::

1. Review the **`## Unreleased changes`** section at the top of the {repo-file}`docs/reference/changelog.md` file and, if necessary, group and/or split entries into relevant subsections (e.g., _Features_, _Docs_, _Bugfixes_, _Security_, etc.). Take a look at previous release notes for guidance and try to keep the format consistent.
2. Review new usages of `.. versionadded::`, `.. versionchanged::`, and `.. deprecated::` directives that were added to the documentation since the last release. If necessary, update the version numbers in these directives to reflect the new release version.
2. [Review](https://github.com/tpvasconcelos/ridgeplot/compare) new usages of `.. versionadded::`, `.. versionchanged::`, and `.. deprecated::` directives that were added to the documentation since the last release. If necessary, update the version numbers in these directives to reflect the new release version.
* You can determine the latest release version by running `git describe --tags --abbrev=0` on the `main` branch. Based on this, you can determine the next release version by incrementing the relevant _MAJOR_, _MINOR_, or _PATCH_ numbers.
3. **IMPORTANT:** Remember to switch to the `main` branch and pull the latest changes before proceeding.
```shell
Expand Down

0 comments on commit 4dd703e

Please sign in to comment.