1 Things to do to release a new version of rt:
3 Build and test candidate packages
5 Read through the README and src/README.txt files for any updates
9 date -R the latest release
11 should be current if this has been updated as each
14 [ Should be automated ]
17 TODO: nothing below this line is accurate for RT
36 Call it something like, "Initialize the new
37 branch." Cause = internal_enhancement. Exempt
38 it from all tests (*_exempt = true).
46 # Change the hard-coded package version numbers
47 # in the following files.
48 aecp rttruct debian/changelog rpm/rt.spec
50 vi rttruct debian/changelog rpm/rt.spec
52 # Optionally, do the same in the following:
53 [optional] aecp HOWTO/change.txt
54 [optional] aecp HOWTO/release.txt
55 [optional] aecp debian/rt.postinst
57 [optional] vi HOWTO/change.txt
58 [optional] vi HOWTO/release.txt
59 [optional] vi debian/rt.postinst
72 Read through the FAQ for any updates
74 Test downloading from the web site download page
77 In the Bugs Tracker, add a Group for the new release (0.05)
79 Announce to the following mailing lists (template below):
81 rt-announce@lists.fsck.com
84 Notify www.cmtoday.com/contribute.html
86 [This guy wants an announcement no more frequently than
87 once a month, so save it for a future release if it's
88 been too soon since the previous one.]
92 [Wait until the morning so the announcement hits the
93 main freshmeat.net page while people in the U.S. are
99 =======================
101 Template release announcement:
105 Version 2.1.XXX of rt has been released and is available for download
106 from the rt web site:
108 http://bestpractical.com/rt/
112 WHAT'S NEW IN THIS RELEASE?
114 Version 2.1.XXX of rt contains the following important changes:
118 For a complete list of changes in version 2.1.XXX, see the CHANGES.txt
119 file in the release itself.