| Kristian Høgsberg | 73dfbd5 | 2014-05-23 10:13:59 -0700 | [diff] [blame] | 1 | To make a release follow these steps. |
| 2 | |
| 3 | 1. Update configure.ac to intended version, commit. |
| 4 | |
| 5 | 2. make distcheck (for weston I do make distcheck TESTS= to avoid |
| 6 | running the tests... most of the tests pass, but the xwayland one |
| 7 | is flaky) |
| 8 | |
| 9 | 3. git tag -am 1.5.0 1.5.0 |
| 10 | |
| 11 | 4. scp tarballs to /srv/wayland.freedesktop.org/www/releases on |
| Daniel Stone | 16a34f1 | 2014-10-08 12:12:41 +0100 | [diff] [blame] | 12 | annarchy.freedesktop.org |
| Kristian Høgsberg | 73dfbd5 | 2014-05-23 10:13:59 -0700 | [diff] [blame] | 13 | |
| 14 | 5. Put SHA1 for tarballs and tagged commits in release announcement |
| 15 | |
| 16 | 6. Push configure.ac commits and tags. |
| 17 | |
| 18 | 7. Send out release announcement. |
| 19 | |
| 20 | 8. Get the release email URL from |
| 21 | http://lists.freedesktop.org/archives/wayland-devel/ |
| 22 | |
| 23 | 9. Update releases.html in wayland-web with links to tarballs and |
| 24 | release email. |
| 25 | |
| 26 | 10. Update topic in #wayland to point to release announcement |
| 27 | |
| 28 | For x.y.0 releases, also create the x.y branch. The x.y branch is for |
| Bryce Harrington | ae71579 | 2015-01-09 18:09:20 -0800 | [diff] [blame] | 29 | bug fixes and conservative changes to the x.y.0 release, and is where |
| Kristian Høgsberg | 73dfbd5 | 2014-05-23 10:13:59 -0700 | [diff] [blame] | 30 | we release x.y.z releases from. Creating the x.y branch opens up |
| 31 | master for new development and lets new development move on. We've |
| 32 | done this both after the x.y.0 release (to focus development on bug |
| 33 | fixing for the x.y.1 release for a little longer) or before the x.y.0 |
| 34 | release (like we did with the 1.5.0 release, to unblock master |
| 35 | development early). |
| 36 | |
| 37 | The master branch configure.ac version should always be (at least) |
| 38 | x.y.90, with x.y being the most recent stable branch. Stable branch |
| 39 | configure version is just whatever was most recently released from |
| 40 | that branch. |
| 41 | |
| 42 | For stable branches, we commit fixes to master first, then cherry-pick |
| 43 | them back to the stable branch. |