~blowry/file

ref: 61fdf66d8623c4b702e1a85fc93144ce00107287 file/RELEASE-PROCEDURE -rw-r--r-- 1.2 KiB
61fdf66dBenjamin Lowry Merge remote-tracking branch 'upstream/master' 1 year, 8 months ago
                                                                                
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
# HOW TO RELEASE FILE

@(#) $File: RELEASE-PROCEDURE,v 1.6 2018/07/25 06:17:15 christos Exp $

1)  Update version number in configure.ac
2)  Note the new version in ChangeLog
3)  Update README if applicable
4)  Commit changes into CVS
5)  Rebuild and run tests (see README.DEVELOPER)
6)  Tag the release with FILEx_yy
7)  Create the source tarball: make distcheck
7a) Sign the source tarball.
	gpg --armor --detach-sign mysoftware-0.4.tar.gz
8)  Make the source tarball available on ftp
9)  Add the new version to bugs.astron.com:
    - Click: Manage > Manage Projects > file
    - Scroll down to "Versions"
    - Click on "Edit" next to the HEAD version
    - Change the "Version" from HEAD to the newly released version
    - Change the "Date Order" to the current time
    - Check the "Released" box
    - Click on "Update Version"
    - Type HEAD into the box at the bottom of the version list and
      click on "Add and Edit Version"
    - Set the "Date Order" to 2030-01-01 (i.e. far in the future)
    - Click on "Update Version"
10) Mail an announcement to file@astron.com containing a summary of the
    ChangeLog changes. Historically we don't mention magic changes in the
    ChangeLog or the mail message, only source changes.