When the Higgins
project was started, Eclipse only offered CVS, not SVN. So even though SVN
has advantages, we had to use CVS. SVN is now available to projects on
request.
SVN has some
features that will give us more control over the build
process.
For example:
Andy "used to use CVS on another project and moved to SVN. Originally his project was
hesitant, but they found that it made doing nightly builds much easier as a
nightly build can be kicked off on a particular revision. Didn't need to
worry about tagging, while letting developers check in ahead of the
builds. Also can get atomic commits (all or nothing).. Also able to
use SVN revision in the file name of a resulting build so that if someone
subsequently reported a bug, we could go back to the exact source for the
build".
On the
Higgins developers call yesterday, we discussed the pros and cons. Dev
notes to follow. We had a guest speaker on the dev call from the Financial
Services Technology Consortium and we agreed to let him review the
notes on his presentation to ensure accuracy, so the notes are
delayed.
