2 - bump version numbers in:
6 - gui/src/BackupWindow.cc (about dialog)
8 - checkout pure CVS and test building everything
9 - checkout pure CVS and:
10 - ./buildgen.sh in root
11 - ./buildgen.sh in opensync-plugin
12 - ./buildgen.sh in gui
13 - remove all autom4te.cache directories
16 Future considerations:
17 - update library's doxygen developer reference on main site,
18 either http://barry.sourceforge.net/ or
19 http://www.netdirect.ca/...somewhere/barry-docs/
20 - update binary packages for each release:
21 - libbarry (deb and rpm)
22 - libbarry-dev.deb and libbarry-devel.rpm
23 - libbarry-doc (deb and rpm) (doxygen tree docs, same as above
25 - barry (or barry-tools?)
26 (command line tools, including bcharge)
28 - barry-backup (GUI backup tool, deb and rpm)
29 - barry-opensync-plugin (deb and rpm)
30 - how many systems do we support?
31 - depends on g++ available on each platform, and which
32 compiler the supporting libs are compiled with
33 - for example, if gtkmm is compiled with g++-3.3,
34 barry and barry-backup should be too
36 - debian stable (sarge at the moment, but new stable
39 - need to check the compiler ABI's to reduce
40 the number of packages needed
42 - only if debian stable packages don't work by