From 396f34e31e37a87537faf87abd4b801e34951e63 Mon Sep 17 00:00:00 2001 From: Tomas Pereira de Vasconcelos Date: Tue, 24 Dec 2024 18:00:47 +0000 Subject: [PATCH] Add link to GH compare --- docs/development/release_process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/development/release_process.md b/docs/development/release_process.md index a37c801..32631f2 100644 --- a/docs/development/release_process.md +++ b/docs/development/release_process.md @@ -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