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 * Adjust shared-library settings, CURRENT:REVISION:AGE in both files,
8 libparted/{fs/,}Makefile.am
9 following the instructions in the comments there.
11 * Run ./configure && make maintainer-clean
13 * Ensure that the desired versions of autoconf, automake, etc.
14 are in your PATH. See the buildreq list in bootstrap.conf for
17 * Ensure that you're on "master" with no uncommitted diffs.
18 This should produce no output: git checkout master; git diff
20 * Run bootstrap one last time. This downloads any new translations:
24 * Pre-release testing:
25 Ensure that make check syntax-check succeeds.
27 * Run "make distcheck"
29 * Set the date, version number, and release type [stable/alpha/beta] on
30 line 3 of NEWS, commit that, and tag the release by running e.g.,
32 build-aux/do-release-commit-and-tag X.Y stable
34 * Run the following to create release tarballs. Your choice selects the
35 corresponding upload-to destination in the emitted gnupload command.
36 The different destinations are specified in cfg.mk. See the definitions
37 of gnu_ftp_host-{alpha,beta,stable}.
39 # "TYPE" must be stable, beta or alpha
42 * Test the tarball. copy it to a few odd-ball systems and ensure that
43 it builds and passes all tests.
45 * While that's happening, write the release announcement that you will
48 Once all the builds and tests have passed,
50 * Run the gnupload command that was suggested by your "make stable" run above.
52 * Wait a few minutes (maybe up to 30?) and then use the release URLs to
53 download all tarball/signature pairs and use gpg --verify to ensure
54 that they're all valid.
56 * Push the NEWS-updating changes and the new tag:
58 v=$(cat .prev-version)
59 git push origin master tag v$v
61 * Announce it on Savannah first, so you can include the preferable
62 savannah.org announcement link in the email message.
65 https://savannah.gnu.org/projects/parted/
66 click on the "submit news", then write something like the following:
67 (If there is no such button, then enable "News" for the project via
68 the Main -> "Select Features" menu item, or via this link:
69 https://savannah.gnu.org/project/admin/editgroupfeatures.php?group=parted)
71 Subject: parted-X.Y released [stable]
73 ...paste the announcement here...
76 Then go here to approve it:
77 https://savannah.gnu.org/news/approve.php?group=parted
79 * Send the announcement email message.
81 * After each non-alpha release, update the on-line manual accessible via
83 http://www.gnu.org/software/parted/manual/
87 build-aux/gnu-web-doc-update