1 Here are most of the steps we (maintainers) follow when making a release.
3 * Start from a clean, up-to-date git directory on "master":
5 make -k maintainer-clean || { ./configure && make maintainer-clean; }
9 * Ensure that the latest stable versions of autoconf, automake, etc.
10 are in your PATH. See the buildreq list in bootstrap.conf for
11 the complete list of tools.
13 * Ensure that you have no uncommitted diffs. This should produce no
18 * Ensure that you've pushed all changes that belong in the release:
20 git push origin master
22 * Check that the NixOS/Hydra autobuilder is reporting all is well:
24 http://hydra.nixos.org/jobset/gnu/@PACKAGE@-master
26 * Run the following command to download any new translations:
28 ./bootstrap && ./configure
30 * Pre-release testing: ensure that the following command succeeds:
32 make check syntax-check distcheck
34 * Set the date, version number, and release type [stable/alpha/beta] on
35 line 3 of NEWS, commit that, and tag the release by running e.g.,
37 build-aux/do-release-commit-and-tag X.Y stable
39 * Run the following to create release tarballs. Your choice selects the
40 corresponding upload-to destination in the emitted gnupload command.
41 The different destinations are specified in cfg.mk. See the definitions
42 of gnu_ftp_host-{alpha,beta,stable}.
44 # "TYPE" must be stable, beta or alpha
47 * Test the tarball. Copy it to a few odd-ball systems and ensure that
48 it builds and passes all tests.
50 * While that's happening, write the release announcement that you will
51 soon post. Start with the template, $HOME/announce-@PACKAGE@-X.Y
52 that was just created by that "make" command.
54 Once all the builds and tests have passed,
56 * Run the gnupload command that was suggested by your "make TYPE" run above.
58 * Wait a few minutes (maybe up to 30?) and then use the release URLs to
59 download all tarball/signature pairs and use gpg --verify to ensure
60 that they're all valid.
62 * Push the NEWS-updating changes and the new tag:
64 v=$(cat .prev-version)
65 git push origin master tag v$v
67 * Announce it on Savannah first, so you can include the savannah.org
68 announcement link in the email message.
71 https://savannah.gnu.org/projects/@PACKAGE@/
72 click on "submit news", then write something like the following:
73 (If there is no such button, then enable "News" for the project via
74 the Main -> "Select Features" menu item, or via this link:
75 https://savannah.gnu.org/project/admin/editgroupfeatures.php?group=@PACKAGE@)
77 Subject: @PACKAGE@-X.Y released [stable]
79 ...paste the announcement here...
82 Then go here to approve it:
83 https://savannah.gnu.org/news/approve.php?group=@PACKAGE@
85 * Send the announcement email message.
87 * After each non-alpha release, update the on-line manual accessible via
89 http://www.gnu.org/software/@PACKAGE@/manual/
93 build-aux/gnu-web-doc-update