(find-maint.info.gz) Making Releases

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