githubmirror/parted

README-release

31 строка1 KB

Jim Meyering

doc: update release procedure to account for soname version number

13 фев 2010, 12:04

13 фев 2010, 12:04f65304f

Here are most of the steps a maintainer followas when making a release.

0. Adjust the shared library version number in libparted/Makefile.am.
   See the three variables there, CURRENT, REVISION, AGE, and follow
   the guidelines in "info libtool".

1. Execute build-aux/parted-release.  `parted-release --help` contains
   additional information.

2. Test the tarball.  Copy it to a few odd-ball systems and ensure that it
   builds and passes all tests.

3. Write the release announcement that will be posted to the mailing lists.
   Start with the generated template in ~/announce-parted-$VERSION.
   Remember to include a description of parted.  You can find this at
   http://www.gnu.org/software/parted/index.shtml

4. Run the gnupload command that was suggested by the release script.  You can
   find this at the end of release.log.

5. Wait a few minutes (maybe up to 30?) and then use the release URLs to
   download all tarball/signature pairs and use gpg --verify to ensure that
   they're all valid.  You will also need these URLs in the announcement mail.

6. Push the new tag with the following command:
     git push origin tag v$VERSION

7. Send the gpg-signed announcement mail, e.g.,
     To: info-gnu@gnu.org, parted-devel@lists.alioth.debian.org
     Cc: coordinator@translationproject.org, bug-parted@gnu.org
     Subject: parted-$VERSION released [stable]