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

On Jul 26, 2008, at 9:40 AM, Lars Strojny wrote:
>
> What about something like that for php-src:
> php-src
>   /trunk
>   /branches
>     /official
>        /5_2
>        /5_3
>     /private
>        /johannes
>        /helly
>   /tags
>     /features
>        /re2c
>        /traits
>     /releases
>        /5
>           /5_3
>              /5_3
>              /5_3_1
>        /6
>          /6_0
>             /6_0
>             /6_0_1
>

While I think we shouldn't limit our freedom too much here (I like  
the idea of thinking outside the box), structures like the above will  
cause a lot of grief if we ever want to move to another revision  
control system that won't recognize the above setup correctly.  It'll  
also make a lot of headaches for developers wanting to import into  
decentralized systems like git etc (just verified this won't work  
with the current git-svn, unless someone knows a way to do this  
easily).  So if we do stray from the standard tags/branches/trunk  
layout it should probably provide us significant benefits rather than  
just a lot of extra organization (IMHO 4 extra subdirs to get to a  
release seems like a lot of hastle with little organizational gain).

I'm also curious how many developers are going to want their own  
"private" branch.  I assume they currently maintain local copies of  
their work in progress and would like to continue to do so?  I also  
tend to think that if they want it checked in that means they are  
working with more than one person which no longer makes it a private  
branch. (?)

-shire