From 044f79d4890a59c474ca2da53ddf6ff6c0b2f0c6 Mon Sep 17 00:00:00 2001 From: Bryce Harrington Date: Fri, 6 Feb 2015 18:01:33 -0800 Subject: releasing: Tweak docs to better match actual workflow --- releasing.txt | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/releasing.txt b/releasing.txt index ce94ed2d..b704725a 100644 --- a/releasing.txt +++ b/releasing.txt @@ -1,14 +1,19 @@ To make a release of Weston and/or Wayland, follow these steps. - 0. Update the first three lines of configure.ac to the intended + 0. Verify the test suites and codebase checks pass. All of the + tests pass should either pass or skip. + + $ make check + + 1. Update the first three lines of configure.ac to the intended version, commit. Also note that Weston includes versioned dependencies on 'wayland-server' and 'wayland-client' in - configure.ac which typically need updated as well. + configure.ac which typically need updated as well. Then commit + your changes: - 1. Verify the test suites and codebase checks pass. (All of the - tests pass should pass except for xwayland, which can be flaky.) - - $ make check + $ git status + $ git commit configure.ac -m "configure.ac: bump to version x.y.z for the xxx release" + $ git push 2. Run the release.sh script to generate the tarballs, sign and upload them, and generate a release announcement template. -- cgit v1.2.1