From 3e25e384b10f3a3a839f20bb1c9825c9b8b5fcfd Mon Sep 17 00:00:00 2001 From: Arman Bilge Date: Tue, 16 Jan 2024 04:03:26 +0000 Subject: [PATCH 1/3] Refine steps about post-release scripts [ci skip] --- RELEASING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/RELEASING.md b/RELEASING.md index dc61fab879..49e71dcd29 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -14,13 +14,13 @@ 1. Publish the release. 1. Wait for all the CI madness to happen, for the release to announced to Discord, and for the artifacts to sync to Maven Central. 1. Make sure you're locally updated and on the right major/minor branch (this is the same branch as step 3). -1. Open a PR to merge the minor branch into the major branch. This is only necessary for patch releases. +1. Run the following script to open two PRs to (1) update the version in the minor branch and then (2) merge the minor branch into the major branch. This script currently works only for patch releases and not for minor releases, milestones, or release candidates, which need special handling. `scripts/make-release-prs.sh ` e.g. `scripts/make-release-prs.sh v3.5.1 v3.5.2` -1. Open a PR to update the version in the README and documentation site. This is only necessary for stable releases (i.e., not Milestones or Release Candidates) +1. Open a PR to the docs branch to update the landing page. This is only necessary for stable releases (i.e., not milestones or release candidates) `scripts/make-site-pr.sh ` From bdb625bb2bdc4d366466b5ef48ac6005f4c53f7e Mon Sep 17 00:00:00 2001 From: Arman Bilge Date: Tue, 16 Jan 2024 04:07:13 +0000 Subject: [PATCH 2/3] Further clarifying [ci skip] --- RELEASING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/RELEASING.md b/RELEASING.md index 49e71dcd29..2453885a54 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -14,7 +14,7 @@ 1. Publish the release. 1. Wait for all the CI madness to happen, for the release to announced to Discord, and for the artifacts to sync to Maven Central. 1. Make sure you're locally updated and on the right major/minor branch (this is the same branch as step 3). -1. Run the following script to open two PRs to (1) update the version in the minor branch and then (2) merge the minor branch into the major branch. This script currently works only for patch releases and not for minor releases, milestones, or release candidates, which need special handling. +1. Run the following script to open two PRs to (1) update the version in README/docs of the minor branch and then (2) merge the minor branch into the major branch. This script currently works only for patch releases and not for minor releases, milestones, or release candidates, which need special handling. `scripts/make-release-prs.sh ` From a83998f0b32c7afb18fe5f6714f2f6111e9ea9df Mon Sep 17 00:00:00 2001 From: Arman Bilge Date: Tue, 16 Jan 2024 04:10:13 +0000 Subject: [PATCH 3/3] Fix typo [ci skip] --- RELEASING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/RELEASING.md b/RELEASING.md index 2453885a54..b7682e952f 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -14,7 +14,7 @@ 1. Publish the release. 1. Wait for all the CI madness to happen, for the release to announced to Discord, and for the artifacts to sync to Maven Central. 1. Make sure you're locally updated and on the right major/minor branch (this is the same branch as step 3). -1. Run the following script to open two PRs to (1) update the version in README/docs of the minor branch and then (2) merge the minor branch into the major branch. This script currently works only for patch releases and not for minor releases, milestones, or release candidates, which need special handling. +1. Run the following script to open two PRs to (1) update the version in the README/docs of the minor branch and then (2) merge the minor branch into the major branch. This script currently works only for patch releases and not for minor releases, milestones, or release candidates, which need special handling. `scripts/make-release-prs.sh `