1 Here are most of the steps a maintainer followas when making a release.
3 0. Adjust the shared library version number in libparted/Makefile.am.
4 See the three variables there, CURRENT, REVISION, AGE, and follow
5 the guidelines in "info libtool".
7 1. Execute build-aux/parted-release. `parted-release --help` contains
8 additional information.
10 2. Test the tarball. Copy it to a few odd-ball systems and ensure that it
11 builds and passes all tests.
13 3. Write the release announcement that will be posted to the mailing lists.
14 Start with the generated template in ~/announce-parted-$VERSION.
15 Remember to include a description of parted. You can find this at
16 http://www.gnu.org/software/parted/index.shtml
18 4. Run the gnupload command that was suggested by the release script. You can
19 find this at the end of release.log.
21 5. Wait a few minutes (maybe up to 30?) and then use the release URLs to
22 download all tarball/signature pairs and use gpg --verify to ensure that
23 they're all valid. You will also need these URLs in the announcement mail.
25 6. Push the new tag with the following command:
26 git push origin tag v$VERSION
28 7. Send the gpg-signed announcement mail, e.g.,
29 To: info-gnu@gnu.org, parted-devel@lists.alioth.debian.org
30 Cc: coordinator@translationproject.org, bug-parted@gnu.org
31 Subject: parted-$VERSION released [stable]