Stanislav Malyshev wrote: >> Switching to subversion would mean a learning curve for some, and a >> change of PHP development tools and practice for _everyone_ involved >> in php.net. It's a major step, particularly at a time when people are > > I used to think so, but my experience working with SVN on Framework > shows it's not that different, at least on the level I use it (and > that'd be the level most other people would use it I guess - > checkout/update/diff/commit). So if we talking learning curve, it's not > that different - svn up vs. cvs up :) I don't know though how (and if at > all possible) to port karma system, changelog, etc. but that's admin > stuff already.
Would be nice if svn already had versioning for metadata, but otherwise it's not that hard to learn (there are even tricks to jump your live tree from a cvs checkout to an svn checkout, although a cvs diff/svn checkout and patch is usually simpler.) The ASF finally set a hard cutoff, and forced the hand. People adapted. In other works, "svn doesn't suck" :) It's just a slightly different tool. svn status is a huge improvement over cvs up to locate the diffs in your current checkout. svn 1.4 finally gives you the chance to mirror the repository. E.g. if you could do it in cvs, you can do it (somehow) finally in svn. The problem, as Rasmus points out, is that a huge repository like php's naturally doesn't migrate cleanly, and that's not even pointing out the nightmares of fat fingers crawling around rcs ,v files. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
