From c93f2f06c99245da0b6ae13350109b42613c27cf Mon Sep 17 00:00:00 2001 From: Sam Lantinga Date: Wed, 4 Jan 2023 23:47:01 -0800 Subject: [PATCH] Updated release_checklist.md for SDL 3.0 --- docs/release_checklist.md | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/release_checklist.md b/docs/release_checklist.md index 37d8b6d94..b1d66f49e 100644 --- a/docs/release_checklist.md +++ b/docs/release_checklist.md @@ -2,7 +2,7 @@ When changing the version, run `build-scripts/update-version.sh X Y Z`, where `X Y Z` are the major version, minor version, and patch level. So -`2 28 1` means "change the version to 2.28.1". This script does much of the +`3 8 1` means "change the version to 3.8.1". This script does much of the mechanical work. @@ -10,9 +10,9 @@ mechanical work. * Update `WhatsNew.txt` -* Bump version number to 2.EVEN.0: +* Bump version number to 3.EVEN.0: - * `./build-scripts/update-version.sh 2 EVEN 0` + * `./build-scripts/update-version.sh 3 EVEN 0` * Do the release @@ -24,9 +24,9 @@ mechanical work. * If it was, do a new feature release (see above) instead -* Bump version number from 2.Y.Z to 2.Y.(Z+1) (Y is even) +* Bump version number from 3.Y.Z to 3.Y.(Z+1) (Y is even) - * `./build-scripts/update-version.sh 2 Y Z+1` + * `./build-scripts/update-version.sh 3 Y Z+1` * Do the release @@ -34,16 +34,16 @@ mechanical work. ## After a feature release -* Create a branch like `release-2.24.x` +* Create a branch like `release-3.4.x` -* Bump version number to 2.ODD.0 for next development branch +* Bump version number to 3.ODD.0 for next development branch - * `./build-scripts/update-version.sh 2 ODD 0` + * `./build-scripts/update-version.sh 3 ODD 0` ## New development prerelease -* Bump version number from 2.Y.Z to 2.Y.(Z+1) (Y is odd) +* Bump version number from 3.Y.Z to 3.Y.(Z+1) (Y is odd) - * `./build-scripts/update-version.sh 2 Y Z+1` + * `./build-scripts/update-version.sh 3 Y Z+1` * Do the release