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