We've implemented CVS and it works great. I suggest the following. Use CVS with a central (server) repository. Give each developer a Spectra installation and a cvs client (http://www.cvsgui.org) that connects to the server repository. Check out your project and work on it locally. Update your work to the server when you're done (automatisch version assignment, patching and all that yazz). Now other developers can update their material with your work. It does require some communication, but that's always the case. In CVS you can update entire local projects to the latest version with a push on the button. When you work on a patch, you use the merge command to merge the patch into the main line of development. All I can say is: make clear agreements on the name of branches and assign them centrally. If you allow people to start using their own branch names like 'john-120101' you can forget about getting an entire patch complete out of the repository.
A good understanding of using tagging, merging and patching in my mind is crucial when you do revision work after a project has been delivered. CVS has made our projects more manageable and version safe. Even though it does require effort to learn the system, it's well worth it. Vriendelijke groet, Marc Schipperheyn <theFactor.e> Premium Partner for Macromedia The future is technological, but it will not be a world of gray steel ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm ------------------------------------------------------------------------------ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
