Alicia, > I already have O'Reilly's Essential CVS book. If you know of any other > CVS resources, such as website links, books, etc. that would help, > would you please reply back via email. Thank you in advance for your help.
I had a hand in writing the eBook "All About CVS" so I'd recommend that one ;) Essential CVS which you already have though has been the one book that most CVS Admins have read for many years though. > CVS Backup Step-by-step guide of how to backup a CVS repository; I thought the ORielly book covered that ? A simple copy or rsync of the repository will do - preferably shut down connections to port 2401 during the copy, but even that's optional... > CVS Security Step-by-step guide on how to prevent the deletion of > files from CVS; How to make files read-only; This is a rather vague question - if you are looking for access control of sandboxes you probably need the CVSAcls script or to migrate to CVSNT (unix/linux/windows, GPL/Free just like CVS but with additional features), if you are wanting to secure the repository itself then that's easy: no user should have be able to login to the box except admins (just disable interactive logins for all normal users). > CVS Best Practices Best practices for merging branches into the > trunk (merge conflicts); It would be nice to know how other companies > are maintaining CVS projects; Again the O'Rielly book or google - generally as a rule though you should look at what business objective your organisation has for implementing SCM, then find a SCM process that supports that objective then implement that process using a set of tools that have the necessary features - copying someone elses process will rarely achieve that result. Regards, Arthur
