1# HOW TO RELEASE FILE 2 3@(#) $File: RELEASE-PROCEDURE,v 1.7 2021/10/18 16:38:25 christos Exp $ 4 51) Update version number in configure.ac 62) Note the new version in ChangeLog 73) Update README.md if applicable 84) Commit changes into CVS 95) Rebuild and run tests (see README.DEVELOPER) 106) Tag the release with FILEx_yy 117) Create the source tarball: make distcheck 127a) Sign the source tarball. 13 gpg --armor --detach-sign mysoftware-0.4.tar.gz 148) Make the source tarball available on ftp 159) Add the new version to bugs.astron.com: 16 - Click: Manage > Manage Projects > file 17 - Scroll down to "Versions" 18 - Click on "Edit" next to the HEAD version 19 - Change the "Version" from HEAD to the newly released version 20 - Change the "Date Order" to the current time 21 - Check the "Released" box 22 - Click on "Update Version" 23 - Type HEAD into the box at the bottom of the version list and 24 click on "Add and Edit Version" 25 - Set the "Date Order" to 2030-01-01 (i.e. far in the future) 26 - Click on "Update Version" 2710) Mail an announcement to file@astron.com containing a summary of the 28 ChangeLog changes. Historically we don't mention magic changes in the 29 ChangeLog or the mail message, only source changes. 30