1 Barry Release Checklist:
2 ------------------------
3 - bump version numbers in
8 - gui/src/BackupWindow.cc (about dialog)
12 - opensync-plugin/configure.ac
13 - opensync-plugin/src/barry_sync.cc
14 - opensync-plugin/configure.ac
15 - opensync-plugin-0.4x/src/barry_sync.cc
16 - opensync-plugin/debian/control (libbarry-dev)
17 - opensync-plugin-0.4x/debian/control (libbarry-dev)
19 - run all tests on a clean git tree, including build test script
20 - write release notes, including contributors, known issues, new
21 features and bugs fixed
22 - include mention of distros that support Barry:
23 (see AUTHORS file for distro list)
24 - include description at the top of what Barry is
26 - bump version number and release date on index.php
27 - update known issues list
28 - check that all external links work, and point to proper content
29 - upload latest web docs to netdirect project page
30 - run: ./static.sh netdirect
31 - upload latest doxygen docs to netdirect project page
32 - update root README file
33 - snip this version's changelog history into its own file
34 - tag CVS repo and sign-tag git repo with latest version
35 - run maintainer/tagged-release.sh
36 - manually push git tags to repo.or.cz and sourceforge.net
37 - upload packages to SourceForge
38 ssh -x -a -2 -t USER,PROJECT@shell.sourceforge.net create
39 then use sf-help for details
40 - Ubuntu: 7.10, 8.04, 9.04
42 - Debian: stable (lenny)
44 - submit tracker news item at SourceForge
45 - send announcement to devel and announce mailing list, including:
48 - URLs to sourceforge and OpenSUSE Build Service binary packages
49 - URL to netdirect doc page
50 - update Freshmeat entry
51 - update Sourceforge screenshots / icons if applicable
52 - send identi.ca/cdfrey and blog notices
53 - update source project, bumping revision numbers in source code
56 A note on the tags in Barry's git repository:
57 ---------------------------------------------
58 Each release will now have at least 3 tags. For example, if releasing
59 version 0.14, the tags will be:
61 barry-0.14 Tag on master branch, signifying the
62 development point that the release occured
63 barry-0.14.tar.bz2 Contains the exact contents of the
64 full tar.bz2 release tarball. If you
65 look far enough in the history logs, you will
66 find the barry-0.14 tag.
67 barry_0.14.orig.tar.gz Contains the exact contents of the debian
68 source package tarball. Again, barry-0.14
69 will be in this tag's history.
71 Basically, the first tag contains only the source code, and no generated
72 files. The second tag (tar.bz2) contains the source code and all
73 generated files. And the third tag (orig) contains all of tar.bz2
74 *except* the debian/ directory. They are arranged so all history
75 merges back into the main non-generated source development tree.