find-maint: Making Releases

1 
1 13 Making Releases
1 ******************
1 
1 This section will explain how to make a findutils release.  For the time
1 being here is a terse description of the main steps:
1 
1   1. Commit changes; make sure your working directory has no uncommitted
1      changes.
1   2. Test; make sure that all changes you have made have tests, and that
1      the tests pass.  Verify this with 'make distcheck'.
1   3. Bugs; make sure all Savannah bug entries fixed in this release are
1      fixed.
1   4. NEWS; make sure that the NEWS and configure.in file are updated
1      with the new release number (and checked in).
1   5. Build the release tarball; do this with 'make distcheck'.  Copy the
1      tarball somewhere safe.
1   6. Tag the release; findutils releases are tagged like this for
1      example: v4.5.5.  Previously a different format was in use:
1      FINDUTILS_4_3_8-1.  You can create a tag with the a command like
1      this: 'git tag -s -m "Findutils release v4.5.7" v4.5.7'.
11   7. Prepare the upload and upload it.  ⇒Automated FTP Uploads
      (maintain)Automated FTP Uploads, for detailed upload instructions.
1   8. Make a release announcement; include an extract from the NEWS file
1      which explains what's changed.  Announcements for test releases
1      should just go to <bug-findutils@gnu.org>.  Announcements for
1      stable releases should go to <info-gnu@gnu.org> as well.
1   9. Bump the release numbers in git; edit the 'configure.in' and 'NEWS'
1      files to advance the release numbers.  For example, if you have
1      just released '4.6.2', bump the release number to '4.6.3-git'.  The
1      point of the '-git' suffix here is that a findutils binary built
1      from git will bear a release number indicating it's not built from
1      the "official" source release.
1   10. Close bugs; any bugs recorded on Savannah which were fixed in this
1      release should now be marked as closed.  Update the 'Fixed Release'
1      field of these bugs appropriately and make sure the 'Assigned to'
1      field is populated.
1