Re: [SVN-MIGRATION] Steps for the SVN migration

Lars Strojny wrote:
> Decisions
> =========
> 1.) Do we want to use mod_dav_svn or svnserve, the subversion daemon?
>   

Having used both, mod_dav_svn is definitely the way to go.  svnserve is 
ok, but ultimately not as elegant of a solution.  The ability to review 
files via http(s) and allow commits via a mounted WebDAV HD for lesser 
technical users can't be passed.


> 2.) Single repository, multiple repositories. Do we want to use a single
> repository for all things PHP, including PEAR, PECL etc.?
>   

I've been on both sides of this as well.  I favor multiple repositories 
as it is a much more elegant solution and has a smaller WTF factor (what 
do you mean I just went from commit 280102 to 301912?  It was only two 
days between commits!)  svn:externals provides a very elegant solution 
for bringing them all into one meta repository that can be checked out 
to grab everything.

Having tags and release branches happen across multiple repositories is 
a bit trickier, though commit hooks can be put in place to make that 
happen as a longer term solution to ease the workload on RMs.  That does 
start to add complexity to the repository and it's associated scripts, 
though.


> 3.) Directory structure: We will have the classical layout
> (branches/tags/trunk), but what about subdirectories in tags like
> releases, and feature tags. What about a developer folder in branches to
> allow developer specific branches?
>   

+1 on the standard Subversion directory structure and give each 
developer their own directories inside branches to create any branches 
they would like.  I don't know if there's really a need for multiple 
directories within tags to group tags together.  Are there that many 
feature tags?  Maybe those could be dropped in features/ and leave full 
releases within the root tags directory.


-T