updated 12/9/05 Name: Move to subversion Vision: Convert to a source code revision tool that provides the access control we need while increasing the efficiency of developers access to the code repository. Mission statement: Replace the CCSM CVS repository with a more modern, easier to use, more robust, easier to maintain, more flexible Software Configuration Management versioning system that meets our needs. Goals: Public accessible (i.e. Free) tool. Allows developer and public access across Internet. Maintains history across directory and file renames Maintains a ChangeLog automatically. Allows simultaneous development similar to current CVS model. Allows several branches of the same code. Allows access control to be different across different branches. Motivation: Scientists want our code repository to have public versions to be accessible by all, but some development versions to be restricted. Everyone also wants the ability to rename files and directories without the current problems of CVS. We also have technical problems with the current system that cause loss of productivity. Plan Currently the plan is to use subversion. We've examined several of the options, and feel subversion is the best open source tool to meet our needs at this time. Arch was a possibility, but it's documentation is lacking and as such subversion looks like a much better way to go. The SWIKI Project on subversion is available from http://swiki.ucar.edu/start/77 Authority: Mariana Vertenstein Project Lead: Mathew Rothstein Scientific Lead: None Schedule: completed Formulate plan of attack -- 1wk x Create source tree for initial port -- 2wks x Iniitial port and test -- 1wk x Evolve projects in svn to latest tags -- 2wks x Finalize subversion environment -- 3wks Resources: Mathew Rothstein Erik Kluzek Brian Eaton Mark Moore Mariana Vertenstein Brian Kauffman Nancy Norton Brian Eaton +all CCSM programmers and developers