RELEASE-PROCEDURE 1.2 KB

1234567891011121314151617181920212223242526272829
  1. # HOW TO RELEASE FILE
  2. @(#) $File: RELEASE-PROCEDURE,v 1.7 2021/10/18 16:38:25 christos Exp $
  3. 1) Update version number in configure.ac
  4. 2) Note the new version in ChangeLog
  5. 3) Update README.md 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. 7a) Sign the source tarball.
  11. gpg --armor --detach-sign mysoftware-0.4.tar.gz
  12. 8) Make the source tarball available on ftp
  13. 9) Add the new version to bugs.astron.com:
  14. - Click: Manage > Manage Projects > file
  15. - Scroll down to "Versions"
  16. - Click on "Edit" next to the HEAD version
  17. - Change the "Version" from HEAD to the newly released version
  18. - Change the "Date Order" to the current time
  19. - Check the "Released" box
  20. - Click on "Update Version"
  21. - Type HEAD into the box at the bottom of the version list and
  22. click on "Add and Edit Version"
  23. - Set the "Date Order" to 2030-01-01 (i.e. far in the future)
  24. - Click on "Update Version"
  25. 10) Mail an announcement to file@astron.com containing a summary of the
  26. ChangeLog changes. Historically we don't mention magic changes in the
  27. ChangeLog or the mail message, only source changes.