Based on feedback from Jim, Russ Sherk and others, we reviewed our SCM plan. However based on our requirements, we need an Administrator/ Reviewer to review the code before it goes to repository.
This is very much required as we have number of programmers, who don't know the whole system and so the implications/ side-effects of their changes in other part of the system. With all your suggestions, I think using branches for individual working and commit may work. I will look at cvs_acls script also. I need to work on whole procedure again.
Sincere thanks to all of you for pointing out the problems in our working.
Abhay Jim Hyslop <address@hidden>
-----BEGIN PGP SIGNED MESSAGE-----
Russ Sherk wrote:
If you have to work like this (because of policy or geography etc.) maybe
> you need to re-think your SCM plan (i.e. CVS may not be the solution for
CVS can still support this mode of working, if you use the cvs_acls
script, allow only the administrator (or check-in person) to check into
HEAD, and allow developers to freely check into any branches.
Dreampossible: Better software. Simply. http://www.dreampossible.ca
Consulting * Mentoring * Training in
C/C++ * OOD * SW Development & Practices * Version Management
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----