docs: update tasks list for release branch (#15025)

cosmos · Feb 14, 2023 · cb23af6 · cb23af6
1 parent 2190974
commit cb23af6
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 17 deletions.
diff --git a/RELEASE_PROCESS.md b/RELEASE_PROCESS.md
@@ -22,11 +22,16 @@ v1.0.0-beta1 → v1.0.0-beta2 → ... → v1.0.0-rc1 → v1.0.0-rc2 → ... →
     * **PRs targeting this branch can be merged _only_ when exceptional circumstances arise**
     * update the GitHub mergify integration by adding instructions for automatically backporting commits from `main` to the `release/vY` using the `backport/Y` label.
 * In the release branch prepare a new version section in the `CHANGELOG.md`
-    * All links must be link-ified: `$ python ./scripts/linkify_changelog.py CHANGELOG.md`
+    * All links must point to their respective pull request.
     * The `CHANGELOG.md` must contain only the changes of that specific released version. All other changelog entries must be deleted and linked to the `main` branch changelog ([example](https://github.com/cosmos/cosmos-sdk/blob/release/v0.46.x/CHANGELOG.md#previous-versions)).
     * Create release notes, in `RELEASE_NOTES.md`, highlighting the new features and changes in the version. This is needed so the bot knows which entries to add to the release page on GitHub.
     * Additionally verify that the `UPGRADING.md` file is up to date and contains all the necessary information for upgrading to the new version.
-* Remove GitHub workflows that should not be in the release branch (eg: `deploy-docs.yml`).
+* Remove GitHub workflows that should not be in the release branch
+    * `deploy-docs.yml`: must be removed to avoid duplicate documentation deployment.
+    * `test.yml`: All standalone go module tests should be removed (expect `./simapp`, and `./tests` and SDK tests).
+        * These packages are tracked and tested directly on main.
+    * `build.yml`: Only the SDK and SimApp needs to be built on release branches.
+        * Tooling is tracked and tested directly on main.
 * Create a new annotated git tag for a release candidate (eg: `git tag -a v1.1.0-rc1`) in the release branch.
     * from this point we unfreeze main.
     * the SDK teams collaborate and do their best to run testnets in order to validate the release.

diff --git a/scripts/linkify_changelog.py b/scripts/linkify_changelog.py