Hi Stas,
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.
It's different if you're someone who doesn't really know what a CVS is and just uses the tool mechanically. That's probably most of the translation teams, some of the documentation teams, a fair proportion of the PEAR and smarty folk.... It's a new tool. Windows-based docs people need to use cygwin to generate a test build on their home pc, so it's a fair bet that most of them will be using commandline cvs without actually understanding it. For svn they'll all be downloading something else they don't really understand (or need to), but that's intimidating for doze people - usually downloading anything via cygwin means downloading about another 8 things that you've no idea about (dependencies). It's actually easier for the coding teams because they can just use tortoisesvn...
Anyway this is 'future talk' so I'll stave off the panic for now :) - Steph -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
