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