gallant/SDL2
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

Moved test/versioning.sh to build-scripts/test-versioning.sh

Browse source 
Reference Issue #6171.
This commit is contained in:
Ryan C. Gordon 2022-09-28 09:09:21 -04:00
parent 4471d22eb6
commit d843d61cc1
No known key found for this signature in database
GPG key ID: FA148B892AB48044
2 changed files with 6 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

0
test/versioning.sh → build-scripts/test-versioning.sh
View file

20
docs/release_checklist.md
View file

@ -1,5 +1,11 @@
# Release checklist
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
mechanical work.
## New feature release
* Update `WhatsNew.txt`
@ -7,9 +13,6 @@
* Bump version number to 2.EVEN.0:
* `./build-scripts/update-version.sh 2 EVEN 0`
* (spaces between each component of the version, and `EVEN` will be a real number in real life.
* Run test/versioning.sh to verify that everything is consistent
* Do the release
@ -22,9 +25,6 @@
* Bump version number from 2.Y.Z to 2.Y.(Z+1) (Y is even)
* `./build-scripts/update-version.sh 2 Y Z+1`
* (spaces between each component of the version, and `Y` and `Z+1` will be real numbers in real life.
* Run test/versioning.sh to verify that everything is consistent
* Do the release
@ -35,19 +35,11 @@
* Bump version number to 2.ODD.0 for next development branch
* `./build-scripts/update-version.sh 2 ODD 0`
* (spaces between each component of the version, and `ODD` will be a real number in real life.
* Run test/versioning.sh to verify that everything is consistent
## New development prerelease
* Bump version number from 2.Y.Z to 2.Y.(Z+1) (Y is odd)
* `./build-scripts/update-version.sh 2 Y Z+1`
* (spaces between each component of the version, and `Y` and `Z+1` will be real numbers in real life.
* Regenerate `configure`
* Run test/versioning.sh to verify that everything is consistent
* Do the release