dothebart: yes, but as I've recently discovered, I am doing it the wrong way.  Whenever we do a release version, I bump the version number of everything in CVS to (version number * 100), with a command like:

cvs commit -r655.0

This is, of course, somewhat stupid.  We have an opportunity to fix that, though, because I am planning to move our source code repository from CVS to Subversion.  We will do whatever is "right" this time.  If you have a way to help automate the release process, please share it.

Reply via email to