|
Reasons for SVN:
- diffs (on the client means faster, offline and less strain on server)
- tagging/branching
- serving via apache2 makes all sorts of things possible (better karma management)
- SVN manipulates the filetypes and does not require any special instructions.
- Directories, renames, etc. are all versioned.
- Ability to use SVK (star merges, and more)
- Ability to do external includes (e.g. pear stuff into pecl/pearweb)
Reasons against SVN:
- larger checkout size
- svn tools not available in all distros by default
- $ID:$ equivalent does not generate consequtive numbering per file
- developers will need to learn to do some things differently
- is svn as flexible with encoding as CVS?
- svn doesn't have real tags
This site powered by YaWiki 0.22 beta.
philip [AT] roshambo [DOT] org
2007-06-03 19:02:34 (309)
This topic was discussed on internals around the end of May 2007 here:
title: better changeset tracking
http://marc.info/?t=118036801200001&r=1&w=2
Many pros and cons are listed and also notice the word "inevitable" is
used at least a few times... ;-)
|
philip [AT] roshambo [DOT] org
2007-04-07 03:01:41 (287)
See Also:
Migrate phpdoc/ to SVN proposal:
* http://doc.php.net/php/rfc/rfc-proposal-show.php?id=8
|
ifeghali [AT] php [DOT] net
2007-03-24 03:48:03 (282)
I am not sure if I am supposed to post my feelings here...
anyway, if we had an election now, I would say:
SVN(-1);
|
php [AT] adamashley [DOT] name
2007-02-06 00:14:18 (265)
Just updating some of these points to current reality:
2. svn tools not available in all distros by default
- long since incorrect, in fact incorrect since before this page was last
edited. most distros have subversion available.
4. developers will need to learn to do some things differently
- The only difference to someone with CVS experience is that svn status
is useful unlike cvs status and that tags and branches have a different
base url.
5. is svn as flexible with encoding as CVS?
- considerably more so. its all hanlded via svn: special properties. and
defaults for these can be set by file type in your .svn configuration.
6. svn doesn't have real tags
- thank god. how many times have you created a tag and need to come back
and turn it into a branch? the under lying system should place limitations
upon how you use it, those limitations should only be agreed upon and
implemented by the people using the system.
I switched to SVN from CVS back before 1.0.0 and have not looked back.
Including on several projects that make PEAR look simple in comparison.
|
arnaud [AT] limbourg [DOT] com
2007-02-03 11:57:40 (263)
Rereading I see that the $Id$ mentions per-file numbering and indeed this
will not be.
|
arnaud [AT] limbourg [DOT] com
2007-02-03 11:54:58 (262)
With keywords you can get the $Id$ replacement working.
|
jacques [AT] php [DOT] net
2007-01-06 21:46:01 (253)
We could use per "subproject" subversion repositories:
http://svn.php.net/bugweb
http://svn.php.net/phpsrc
http://svn.php.net/phpweb
http://svn.php.net/pear
etc.
|
Add A Comment
Your comment will be added immediately; please check your comments, and be nice. :-)
Please use plain text only; HTML and PHP code will be converted to entities.
Your email address will be obfuscated with [AT] and [DOT] after you post your comment.
|
|