3 @(#) $File: RELEASE-PROCEDURE,v 1.6 2018/07/25 06:17:15 christos Exp $
5 1) Update version number in configure.ac
6 2) Note the new version in ChangeLog
7 3) Update README if applicable
8 4) Commit changes into CVS
9 5) Rebuild and run tests (see README.DEVELOPER)
10 6) Tag the release with FILEx_yy
11 7) Create the source tarball: make distcheck
12 7a) Sign the source tarball.
13 gpg --armor --detach-sign mysoftware-0.4.tar.gz
14 8) Make the source tarball available on ftp
15 9) 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"
27 10) 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.