-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 mthread wrote: > Hi, > thanx for the reply. But I am curious how so many projects are > handled using CVS. I am sure every project development team must be > implementing the sort of policy we are looking to implement. Hope more > guys give their ideas for this topic.
It can be summed up in one word: trust. Trust your people to follow the rules. You can set up the system so that the testing team cannot change the repository, but only check out. Once you've done that, does it really matter if they use "export" or "checkout"? Actually, I would think you'd /want/ them to use checkout - that way you can verify exactly which version they've checked out. If the testers end up with version x.y.3 but they're supposed to be testing x.y.4, you have to do a lot more digging to figure out whether the tester exported the wrong version, or whether the developers forgot to increment the build number. - -- Jim Hyslop 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 Mozilla - http://enigmail.mozdev.org iD8DBQFG6nIwLdDyDwyJw+MRAszVAKC9LDXCOjk/yTh6++taMCy95I68mQCgvaJT zbUO0hbyVs0gc1yRpBMp+bs= =88Ci -----END PGP SIGNATURE-----
