-
CVS Advice
I'm changing jobs again, going back to a former employer who's asked me to come back.
I need to do a lot of restructuring while I'm there, part of that is implementing a version control system. However, outside of SourceSafe, I have very little experience with them.
Core requirements:
1.) Must be able to accommodate in-office staff, as well as external contractors. We should always be able to get the latest version of stuff from our contractors, and always be able to roll back.
2.) Must support any file type: we have Word document scripts, .fla's, audio files, images, xml, html, js, FlashForm source.
3.) External contractors will submit both updated source and published files.
4.) External contractors may be retarded and should not be able to roll back.
5.) Must be able to support instances of projects: e.g. we have a stock generic course, then have a copy of it for a client that goes through a customization process.
6.) Must be able to archive client projects. That is, they are preserved, but hidden from view after awhile, or moved to an archive section.
7.) Must be able to have access control per project. In particular, there is an on-going ColdFusion product that will be managed through it by a single person, me, who needs a complete change history of every file.
8.) Must integrate with CS3, at least Dreamweaver.
I also need advice on how to best set this up, system requirements, and best practices.
Any takers? PM me.
-
-
-
As the article suggests right off, Subversion (SVN) is the way to go. I can't say that I'm an expert on the finer points of setting it up, etc. But, the manual is freely available here: http://svnbook.red-bean.com/
