blob: c0d60f4062aa642ef0a5216468d13ff07cfae85f (
plain) (
blame)
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
|
libopenmpt release process
==========================
0.3
---
For libopenmpt 0.3, see
https://source.openmpt.org/svn/openmpt/branches/OpenMPT-1.27/doc/libopenmpt_release.txt
.
0.4
---
For libopenmpt 0.4, see
https://source.openmpt.org/svn/openmpt/branches/OpenMPT-1.28/doc/libopenmpt_release.txt
.
0.5
---
For libopenmpt 0.4, see
https://source.openmpt.org/svn/openmpt/branches/OpenMPT-1.29/doc/libopenmpt_release.txt
.
0.6
---
1. ensure that the OpenMPT version is preferrably at a aa.bb.cc.00 version,
otherwise increment the minorminor part to a new value used specifically for
the libopenmpt release
2. from a clean checkout, run (requires xpath!!!)
./build/svn/do_libopenmpt_release.sh
3. website: add release announcement
4. website: update download links
5. wait for buildbot
6. in a website checkout, run (as printed by the release script)
./release-0.5.sh $NEWVER +release
7. increment OpenMPT version minorminor in `common/versionNumber.h` when all
releases are done on the svn side (either libopenmpt only, or both
libopenmpt and OpenMPT)
release candidate
-----------------
1. `./build/update_libopenmpt_version.sh release-rc 1`
2. `svn commit -m '[Mod] libopenmpt: Bump rc version.'`
3. `./build/svn/do_libopenmpt_release_rc.sh`
4. `./build/update_libopenmpt_version.sh release-rc 2`
5. `svn commit -m '[Mod] libopenmpt: Bump rc version.'`
|
