We just closed an evaluation of source management systems, and the good
news is that we are sticking with CVS, Rational ClearCase lost the race. One
thing we learnt, though, from talking and reading is that a lot of ClearCase
customers take the time to define a process around the product, supported
by shell-scripts, triggers, and whatnot. We feel that we want to do the
same to CVS, so I am currently busy writing a shell around CVS (in Python)
that offers an activity-based interface to the repository. The user typically
won't say "I want to create a branch", but rather "I want to start working
on bugfix xyz" - the shell will take care of branching, deciding when and
what to merge, etcetera. I'm also planning a close integration with the
bug tracking system we use, Bugzilla (so that a developer can click a button
"Start work on this bug", which results in creating a branch etcetera).
I'll be selling this internally as an ideal candidate for an open source
solution - after a bit of initial hacking, I'd like to drop the stuff on
SourceForge under a BSD or GNU license. Now I cannot promise that I'll be
able to pull this through, but it would help me if there would be lots
of interest to actually use this stuff in the CVS community. Would
people consider/like to/love to switch to a more process-based shell
around CVS? Or is the general feeling that this sort of stuff ain't
necessary?
--
Cees de Groot http://www.cdegroot.com <[EMAIL PROTECTED]>
GnuPG 1024D/E0989E8B 0016 F679 F38D 5946 4ECD 1986 F303 937F E098 9E8B
Forge your CipherSaber and list it: http://www.xs4all.nl/~cg/ciphersaber/
