I apologize in advance for jumping into this thread so late (finally
trying to catch up on internals@).
FWIW, I'd also like to move to SVN, eventually (and inevitably (-: ).
I've opposed this move for php.net in the past, but only because the
proposals I was fighting were for a partial conversion (e.g. I was
against moving /only/ phpdoc (and associated modules) to svn).
Some of the things that would directly benefit the project:
+ svn:externals instead of CVSROOT/modules is much cleaner and more
robust
+ sane hooks mechanism
+ sane svn output parsing for scripts
+ better and real (ie, not hacked on) support for users and ACLs
+ revision numbering (useful for some phpdoc tools)
+ SVN is (mostly) intuitive for CVS users. The process is nearly the
same, and it's not a big shift like git or darcs, etc.
+ offline diff and status
The big negatives are of course:
- We lose real tagging
~ sort of. We could restrict the subproject/tags ACL to release
manager(s), and each commit gets a revision so that could serve as a
"real" tag for people who want to (e.g.) tag "PRE-DOC-SPLIT".
- We will lose commit history on some files
+ ESPECIALLY for the ugly symlinks and moves from php-src to PECL.
This is going to be a mess.
- The development process will be affected
+ Specifically, it's going to be a big pain to stop all commits while
we do the switch, and then sync everyone up afterwards.
S
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
