File: release_checklist.md

package info (click to toggle)
libsdl3 3.2.28%2Bds-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 42,080 kB
  • sloc: ansic: 391,330; objc: 12,361; xml: 9,084; cpp: 5,729; perl: 4,589; python: 3,373; sh: 1,032; makefile: 265; cs: 56
file content (52 lines) | stat: -rw-r--r-- 1,468 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
# Release checklist

* Run `build-scripts/create-release.py -R libsdl-org/SDL --ref <branch>` to do
  a dry run creating the release assets. Verify that the archives are correct.

* Tag the release, e.g. `git tag release-3.8.0; git push --tags`

* Run `build-scripts/create-release.py -R libsdl-org/SDL --ref <release-tag>`
  to have GitHub Actions create release assets. This makes sure the revision
  string baked into the archives is correct.

* Verify that the source archive REVISION.txt has the correct release tag.

* Sign the source archives and upload everything to libsdl.org

* Create a GitHub release and attach the archives you just generated.

## New feature release

* Update `WhatsNew.txt`

* Bump version number to 3.EVEN.0:

    * `./build-scripts/update-version.sh 3 EVEN 0`

* Do the release

* Immediately create a branch for patch releases, e.g. `git branch release-3.EVEN.x`

* Bump version number from 3.EVEN.0 to 3.(EVEN+1).0

    * `./build-scripts/update-version.sh 3 EVEN+1 0`

* Update the website file include/header.inc.php to reflect the new version

## New bugfix release

* Bump version number from 3.Y.Z to 3.Y.(Z+1) (Y is even)

    * `./build-scripts/update-version.sh 3 Y Z+1`

* Do the release

* Update the website file include/header.inc.php to reflect the new version

## New development prerelease

* Bump version number from 3.Y.Z to 3.Y.(Z+1) (Y is odd)

    * `./build-scripts/update-version.sh 3 Y Z+1`

* Do the release