1 Barry Release Checklist:
2 ------------------------
3 - bump version numbers in
5 - configure.ac (2 places)
7 - opensync-plugin/configure.ac
8 - opensync-plugin-0.4x/configure.ac
9 - desktop/configure.ac (2 places)
19 - debian/control (major version only)
20 - debian/libbarry*.* (files need to be renamed)
21 - debian/rules (the barry18 includedir)
23 - opensync-plugin/debian/changelog
24 - opensync-plugin/debian/control (libbarry-dev)
26 - opensync-plugin-0.4x/debian/changelog
27 - opensync-plugin-0.4x/debian/control (libbarry-dev)
31 - test ABI / API and bump major or minor version as appropriate
32 - run all tests on a clean git tree, including build test script
33 - write release notes, including contributors, known issues, new
34 features and bugs fixed
35 - include mention of distros that support Barry:
36 (see AUTHORS file for distro list)
37 - include description at the top of what Barry is
39 - bump version number and release date on index.php
40 - update known issues list
41 - check that all external links work, and point to proper content
42 - upload latest web docs to netdirect project page
43 - run: ./static.sh netdirect
44 - upload latest doxygen docs to netdirect project page
45 - update root README file
46 - snip this version's git shortlog history into its own file
47 - sign-tag git repo with latest version
48 - no need to run maintainer/tagged-release.sh since you're maintainer now
49 - manually push git tags to repo.or.cz and sourceforge.net
50 - upload packages to SourceForge
51 ssh -x -a -2 -t USER,PROJECT@shell.sourceforge.net create
52 then use sf-help for details
53 MAKE SURE that the tar source files are under
54 /files/barry/barry-{version}/barry_{version}.tar.gz,
55 so that debian/watch remains accurate
56 - Ubuntu: 7.10, 8.04, 9.04
58 - Debian: stable (lenny)
60 - upload binary packaging metadata to download.barry.netdirect.ca
61 under a versioned directory (barry-0.18.0/) and update the
63 - remember to run make-redirect.sh for both the new release
65 - add the new release to .htaccess, and replace barry-latest
66 redirect links with the new ones
67 - make backup of new htaccess
68 - send announcement to devel and announce mailing list, including:
71 - URLs to sourceforge and OpenSUSE Build Service binary packages
72 - URL to netdirect doc page
73 - submit tracker news item at SourceForge
74 - update Freshmeat entry
75 - update Sourceforge screenshots / icons if applicable
76 - send identi.ca/cdfrey and blog notices
77 - update source project, bumping revision numbers in source code
80 A note on the tags in Barry's git repository:
81 ---------------------------------------------
82 Each release will now have at least 3 tags. For example, if releasing
83 version 0.14, the tags will be:
85 barry-0.14 Tag on master branch, signifying the
86 development point that the release occured
87 barry-0.14.tar.bz2 Contains the exact contents of the
88 full tar.bz2 release tarball. If you
89 look far enough in the history logs, you will
90 find the barry-0.14 tag.
91 barry_0.14.orig.tar.gz Contains the exact contents of the debian
92 source package tarball. Again, barry-0.14
93 will be in this tag's history.
95 Basically, the first tag contains only the source code, and no generated
96 files. The second tag (tar.bz2) contains the source code and all
97 generated files. And the third tag (orig) contains all of tar.bz2
98 *except* the debian/ directory. They are arranged so all history
99 merges back into the main non-generated source development tree.