From: Martin K. <mar...@fe...> - 2007-11-18 19:35:14
|
Hi there, after doing some maintenance work, I've been stumbling accross some of the limitations of CVS. As I'm (both private and professionally) am using subversion for all other projects, I'd like to move SOAP-Lite's repository to SVN, too. Theres two main reasons for doing so: * Accessibility via HTTP(S) Subversion on SF.net can be accessed via http(s). To me it means that I can access SOAP-Lite's repository from everywhere. Right now I'm sometimes having troubles to connect through company firewalls. * Lazyness SVN keeps a global revision number (and a global revision log) for the whole repository. When compiling the Changes file for a release, yll a maintainer has to do is typing "svn history" and look through the commit messages. This is impossible with CVS, as CVS keeps a log for every file. There's a few other reasons I'm not going to discuss in detail - if you need more info on differences between CVS and SVN, just ask. SF.net provides SVN repositories, and instruction on how to migrate (using cvs2svn - I have been migrating the twentysomething repositories of my former team with cvs2svn without having troubles). If there's no opinions against the migration, I'll proceed - please let me know your thoughts. Thanks, Martin |