From 7824c19c69726563547c9e1f1843fb2f1f058418 Mon Sep 17 00:00:00 2001 From: Even Rouault Date: Sat, 16 Nov 2024 14:43:12 +0100 Subject: [PATCH 1/2] Update HOWTO-RELEASE.md regarding auto_tag_stable.yml Update the procedure to update the workflow that automatically refreshes the "stable" tag from commits in the current release branch. --- HOWTO-RELEASE.md | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/HOWTO-RELEASE.md b/HOWTO-RELEASE.md index 36495b7302..e40245e8b0 100644 --- a/HOWTO-RELEASE.md +++ b/HOWTO-RELEASE.md @@ -149,7 +149,13 @@ Barring a successful promotion process we can proceed with the final release. See step 1.6 above. Do not rename the archives with RC postfixes. -### 2.2 Update website + +### 2.2 Update the STABLE_BRANCH repository variable + +Go to https://github.com/OSGeo/PROJ/settings/variables/actions/STABLE_BRANCH +and update the value to be x.y + +### 2.3 Update website - Add the release notes from `NEWS.md` to `docs/source/news.rst` @@ -165,7 +171,7 @@ See step 1.6 above. Do not rename the archives with RC postfixes. When pushed upstream the website will be update to the current version. -### 2.3 Tag the release +### 2.4 Tag the release Tag the release with: @@ -174,13 +180,13 @@ git tag -a -m "Create tag x.y.z" x.y.z git push --tags ``` -### 2.4 Check the GitHub Zeonodo integration +### 2.5 Check the GitHub Zeonodo integration Go to https://zenodo.org/account/settings/github/ and check that the OSGeo/PROJ repository is ON so that the creation of the GitHub release triggers the creation of a corresponding Zenodo record. -### 2.5 Prepare the release on GitHub +### 2.6 Prepare the release on GitHub When the new tag is pushed upstream GitHub picks up that a new release has been issued. Update the new release on with @@ -188,7 +194,7 @@ the release notes from `NEWS.md` and add the prepared source distribution archiv to the release (otherwise GitHub will just package the entire repository - we don't want that). -### 2.6 Announce the new release +### 2.7 Announce the new release The release should be announced on PROJ and MetaCRS mailing lists. Additionally the release announcement should be sent to which will add From bb24e728cce9cbcce165808b95d41e671d1a045c Mon Sep 17 00:00:00 2001 From: Even Rouault Date: Sat, 16 Nov 2024 18:32:53 +0100 Subject: [PATCH 2/2] HOWTO-RELEASE.md: remove lines about RtD changes no longer needed --- HOWTO-RELEASE.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/HOWTO-RELEASE.md b/HOWTO-RELEASE.md index e40245e8b0..5b9d1ed8cc 100644 --- a/HOWTO-RELEASE.md +++ b/HOWTO-RELEASE.md @@ -234,9 +234,3 @@ versions. Versions are based on branch labels, e.g. "9.2". To modify settings, registered users must first log in. To add a version, go to and click "Activate" next to the maintenance branch label. - -Also update the redirect for `/* -> /en/X.Y/:splat` at - - -The latest maintenance branch should be set as the "Default version" found at -