NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
:-)
--Larry Wall in <1991May31.181659.28817@jpl-devvax.jpl.nasa.gov>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
CVS Best Practices (Score:1)
CVS Best Practices [tldp.org] is something you probably already have read. If not, I highly recommend it. As I am writting this, I notice it is not version 1.4, and last I read it was 1.3, so it is a working document.
Also, I found the A.C.M.E. [cmcrossroads.com] website helpful. A.C.M.E. stands for Assembling Configuration Management Environments (for Software Development). Most of this stuff is theory, since "Configuration Management" is usualy a set of tools, and not one huge utility (unless you count ClearCase, but that is a beast left elsewhere).
At my job I think we are going to go with the branch per release, and fix a bug on a release, and then merge back into the HEAD (unless the bug does not exist in the HEAD branch). The actual process is not in place, and only a small set of developers are using CVS, since we have some old legacy in house CM type system, that just reaks of problems (and has been demostrated to have a ton of them). And there are a bunch of other little balls of wax I won't go into.
Best of luck.
Reply to This
Re:CVS Best Practices (Score:1)
Thanks for the comments, exeunt. I'm not really doing much CVS management these days. I ultimately made a decision, we went with it, and it's working pretty well. I imagine that if I get back into the fray, I'll be checking out your links.