Dean, >I have a question on access control. Is there a way to prevent all commits >on the main trunk and allow commits on branches only? Once the changes on >the branch are reviewed and approved for merging into the main trunk, then >the main trunk can be manually opened up temporarily for those changes only.
If you are using CVSHOME CVS (1.11 or 1.12) you will want to look into the SetACLs scripts. CVSNT server (free/GPL) on Linux/Unix/Windows/Mac has a "cvs chacl" command for setting access control lists. There was a very long discussion about whether it is "better" to perform development on the trunk or on the branch (and merge into Trunk) about six to twelve months ago on the CVSNT list. It was very good reading and I suggest you have a read before making a final decision on the methodology. The archives are here: http://www.cvsnt.org/pipermail/cvsnt/ Regards, Arthur Barrett _______________________________________________ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs