RELEASE-PROCEDURE 1.1 KB

123456789101112131415161718192021222324252627
  1. # HOW TO RELEASE FILE
  2. @(#) $File: RELEASE-PROCEDURE,v 1.2 2014/03/16 08:56:36 kim Exp $
  3. 1) Update version number in configure.ac
  4. 2) Note the new version in ChangeLog
  5. 3) Update README if applicable
  6. 4) Commit changes into CVS
  7. 5) Rebuild and run tests (see README.DEVELOPER)
  8. 6) Tag the release with FILEx_yy
  9. 7) Create the source tarball: make distcheck
  10. 8) Make the source tarball available on ftp
  11. 9) Add the new version to bugs.gw.com:
  12. - Click: Manage > Manage Projects > file
  13. - Scroll down to "Versions"
  14. - Click on "Edit" next to the HEAD version
  15. - Change the "Version" from HEAD to the newly released version
  16. - Change the "Date Order" to the current time
  17. - Check the "Released" box
  18. - Click on "Update Version"
  19. - Type HEAD into the box at the bottom of the version list and
  20. click on "Add and Edit Version"
  21. - Set the "Date Order" to 2030-01-01 (i.e. far in the future)
  22. - Click on "Update Version"
  23. 10) Mail an announcement to file@mx.gw.com containing a summary of the
  24. ChangeLog changes. Historically we don't mention magic changes in the
  25. ChangeLog or the mail message, only source changes.