1 Barry Release Checklist:
2 ------------------------
3 - bump version numbers in
4 Note: make sure you check all control files below for both current
5 versions (i.e. libbarry0 (>= 0.18)) and the next version
6 (i.e. libbarry0 (<< 0.19)) since the binary packages should prevent
7 interaction with incompatible libraries this way.
10 - gui/src/BackupWindow.cc (about dialog)
11 - desktop/src/Makefile.am (oswrapper lib version & include dir)
15 - debian/control (libbarry0 should not depend on minor number)
16 - debian/rules (the barry18 includedir)
17 - opensync-plugin/configure.ac
18 - opensync-plugin/src/barry_sync.cc
19 - opensync-plugin-0.4x/configure.ac
20 - opensync-plugin-0.4x/src/barry_sync.cc
21 - opensync-plugin/debian/control (libbarry-dev)
22 - opensync-plugin/debian/changelog (libbarry-dev)
23 - opensync-plugin-0.4x/debian/control (libbarry-dev)
24 - opensync-plugin-0.4x/debian/changelog (libbarry-dev)
26 - desktop/src/barrydesktop.cc
27 - test ABI / API and bump major or minor version as appropriate
28 - run all tests on a clean git tree, including build test script
29 - write release notes, including contributors, known issues, new
30 features and bugs fixed
31 - include mention of distros that support Barry:
32 (see AUTHORS file for distro list)
33 - include description at the top of what Barry is
35 - bump version number and release date on index.php
36 - update known issues list
37 - check that all external links work, and point to proper content
38 - upload latest web docs to netdirect project page
39 - run: ./static.sh netdirect
40 - upload latest doxygen docs to netdirect project page
41 - update root README file
42 - snip this version's changelog history into its own file
43 - tag CVS repo and sign-tag git repo with latest version
44 - run maintainer/tagged-release.sh
45 - manually push git tags to repo.or.cz and sourceforge.net
46 - upload packages to SourceForge
47 ssh -x -a -2 -t USER,PROJECT@shell.sourceforge.net create
48 then use sf-help for details
49 MAKE SURE that the tar source files are under
50 /files/barry/barry-{version}/barry_{version}.tar.gz,
51 so that debian/watch remains accurate
52 - Ubuntu: 7.10, 8.04, 9.04
54 - Debian: stable (lenny)
56 - submit tracker news item at SourceForge
57 - send announcement to devel and announce mailing list, including:
60 - URLs to sourceforge and OpenSUSE Build Service binary packages
61 - URL to netdirect doc page
62 - update Freshmeat entry
63 - update Sourceforge screenshots / icons if applicable
64 - send identi.ca/cdfrey and blog notices
65 - update source project, bumping revision numbers in source code
68 A note on the tags in Barry's git repository:
69 ---------------------------------------------
70 Each release will now have at least 3 tags. For example, if releasing
71 version 0.14, the tags will be:
73 barry-0.14 Tag on master branch, signifying the
74 development point that the release occured
75 barry-0.14.tar.bz2 Contains the exact contents of the
76 full tar.bz2 release tarball. If you
77 look far enough in the history logs, you will
78 find the barry-0.14 tag.
79 barry_0.14.orig.tar.gz Contains the exact contents of the debian
80 source package tarball. Again, barry-0.14
81 will be in this tag's history.
83 Basically, the first tag contains only the source code, and no generated
84 files. The second tag (tar.bz2) contains the source code and all
85 generated files. And the third tag (orig) contains all of tar.bz2
86 *except* the debian/ directory. They are arranged so all history
87 merges back into the main non-generated source development tree.