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