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