root/lm-sensors/branches/lm-sensors-3.0.0/doc/developers/release_checklist @ 5043

Revision 5043, 1.9 KB (checked in by khali, 8 years ago)

Create a new version in track after each release.

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
4Release steps:
5- Check out lm-sensors
6- Update if necessary, the version number of libsensors
7  (edit lib/ and change LIBMAINVER and/or LIBMINORVER)
8  Remember: update main number when interface changes, minor if new
9  functionality is added, and patch if only bugs are fixed.
10  `svn diff -r Vx-y-z lib' is your friend.
11- Update the CHANGES file (add the release date)
12- Update lm_sensors.lsm (Version, Entered-date and Primary-site)
13- Update version.h
14- Commit
15- Tag the release using SVN:
16  svn copy \
17 \
18      -m "3.x.x release"
20- Move to a temporary directory and get a copy of the freshly tagged code:
21  svn export lm_sensors-3.x.x
22- Tar it up:
23  tar jcf lm_sensors-3.x.x.tar.bz2 lm_sensors-3.x.x
24- Sign it:
25  gpg -b lm_sensors-3.x.x.tar.bz2
26- Post it:
27  scp lm_sensors-3.x.x.tar.bz2* \
29- Set correct permissions:
30  ssh chmod 664 \
31      '/srv/*'
33After release, remember to:
34- Copy to mirrors
35- Update the Download page on, then add a news item
36- Announce on Freshmeat
37- Add "+SVN" to version.h
38- Mark the corresponding release milestone as complete using trac-admin
39  e.g. 'trac-admin /srv/ milestone completed 3.0.0 2007-11-24'
40- Create a new version for the bug tracking system using trac-admin
41  e.g. 'trac-admin /srv/ version add 3.0.0 2007-11-24'
42- Create a new release milestone using trac-admin
43  e.g. 'trac-admin /srv/ milestone add 3.0.1 2008-02-15'
44- Send lm_sensors.lsm to the LSM by mailing it to with the
45  subject `add' (no quotes)
Note: See TracBrowser for help on using the browser.