1 Here are most of the steps we (maintainers) follow when making a release.
3 * start from a clean, up-to-date git directory.
5 git checkout master; git pull
7 * Run ./configure && make maintainer-clean
9 * Ensure that the desired versions of autoconf, automake, bison, etc.
10 are in your PATH. See the buildreq list in bootstrap.conf for
13 * Ensure that you're on "master" with no uncommitted diffs.
14 This should produce no output: git checkout master; git diff
16 * Run bootstrap: ./bootstrap
18 FIXME: enable excluded programs like arch? to get their manual pages?
20 * Pre-release testing:
21 Ensure that make check syntax-check succeeds.
22 On at least one SELinux-enabled (enforcing) and one non-SELinux system,
23 run all tests, both root-only and regular.
24 Run *all* non-root tests, including expensive and very expensive ones i.e.,
25 run this: make -j1 check RUN_VERY_EXPENSIVE_TESTS=yes RUN_EXPENSIVE_TESTS=yes
27 Run the root-only tests:
28 sudo env PATH="$PATH" NON_ROOT_USERNAME=$USER make -k check-root
30 * Run "make distcheck"
32 * Manually set the date, version number, and [stable/alpha/beta] on
33 line 3 of NEWS, then do e.g.,:
36 pkg=$(sed -n 's/^PACKAGE = \(.*\)/\1/p' Makefile)
37 git commit -F <(printf 'version '$v'\n\n* NEWS: Record release date.\n') -a
38 git tag -s -m "$pkg $v" v$v HEAD
40 * Run the following to create release tarballs. Your choice selects the
41 corresponding upload-to destination in the emitted gnupload command.
42 The different destinations are specified in cfg.mk. See the definitions
43 of gnu_ftp_host-{alpha,beta,stable}.
45 # "TYPE" must be stable, beta or alpha
48 * Test the tarball. copy it to a few odd-ball systems and ensure that
49 it builds and passes all tests.
51 * While that's happening, write the release announcement that you will
54 Once all the builds and tests have passed,
56 * Run the gnupload command that was suggested by your "make major" 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.
64 v=$(cat .prev-version)
65 git push origin tag v$v
67 * Send the gpg-signed announcement mail, e.g.,
69 To: info-gnu@gnu.org, coreutils-announce@gnu.org
70 Cc: coordinator@translationproject.org, bug-coreutils@gnu.org
71 Subject: coreutils-8.0 released [beta]
73 * Approve the announcement here:
74 http://lists.gnu.org/mailman/admindb/coreutils-announce
76 * Announce it on Savannah, too:
78 https://savannah.gnu.org/projects/coreutils/
79 click on the "submit news", then write something like the following:
80 (If there is no such button, then enable "News" for the project via
81 the Main -> "Select Features" menu item, or via this link:
82 https://savannah.gnu.org/project/admin/editgroupfeatures.php?group=gzip)
84 Subject: coreutils-0.0 released [beta]
85 The announcement is here:
86 http://article.gmane.org/gmane.comp.gnu.core-utils.announce/54
88 Then go here to approve it:
89 https://savannah.gnu.org/news/approve.php?group=coreutils
91 * After each non-alpha release, update the on-line manual accessible via
93 http://www.gnu.org/software/coreutils/manual/
97 build-aux/gnu-web-doc-update