1# Releasing 2 3To make a release of libdisplay-info, follow these steps. 4 50. Verify the test suites and codebase checks pass. All of the tests should 6 either pass or skip. 7 8 ninja -C build/ test 9 101. Update the first stanza of `meson.build` to the intended version. 11 12 Then commit your changes: 13 14 RELEASE_NUMBER="x.y.z" 15 RELEASE_NAME="[alpha|beta|RC1|RC2|official|point]" 16 git status 17 git commit meson.build -m "build: bump to version $RELEASE_NUMBER for the $RELEASE_NAME release" 18 git push 19 202. Run the `release.sh` script to generate the tarballs, sign and upload them, 21 and generate a release announcement template. 22 233. Compose the release announcements. The script will generate a 24 libdisplay-info-x.y.z.announce file with a list of changes and tags. Prepend 25 these with a human-readable listing of the most notable changes. For x.y.0 26 releases, indicate the schedule for the x.y+1.0 release. 27 284. PGP sign the release announcement and send it to 29 <wayland-devel@lists.freedesktop.org>. 30 31For x.y.0 releases, also create the release series x.y branch. The x.y branch 32is for bug fixes and conservative changes to the x.y.0 release, and is where we 33create x.y.z releases from. Creating the x.y branch opens up main for new 34development and lets new development move on. 35 36 git branch x.y [sha] 37 git push origin x.y 38 39For stable branches, we commit fixes to main first, then `git cherry-pick -x` 40them back to the stable branch. 41 42