Re: [SVN-MIGRATION] Proposed repository structure

Hello Gwynne, Monday, September 1, 2008, 11:05:56 PM, you wrote: > I apologize to everyone for being out of the loop for so long; I had > some personal issues come up. In any case, I've been talking with > Johannes and Pierre, and we've come up with the following proposed SVN > repository structure. Comments are invited and encouraged. > - All projects will use the standard SVN trunk/ tags/ branches/ > structure. > Pros: Works with various tools that expect it, mirrors CVS' > behavior for those not used to SVN > Cons: Less flexible > - Zend and TSRM will remain separate projects from php-src/ > Pros: Again, mirrors the old CVS layout > Cons: It's ugly! > - All -web/ projects will lose the -web/ suffix and be put under a > web/ master directory. > Pros: Organizationally more structured > Cons: It's a change from CVS > - Obsolete projects which aren't touched anymore will NOT be converted > from CVS > Pros: Avoids clutter in SVN > Cons: CVS would have to be maintained indefinitely to preserve the > history > Here's a quick overview of the proposed root of the SVN repository: > pear/ > <various pear modules> > pecl/ > <various pecl modules> > php-doc/ > php-src/ > tsrm/ > web/ > php/ > php-doc/ > php-master/ > smarty/ > <etc.> > zend/ <this will be Zend 2> Here are my points in case anyone is intersted: 1) Copy everything to SVN, it doesn't hurt having a few more things there, if they won't be used, they won't be... if they are, they are at least available. Maybe have a top level /old-stuff 2) Move Zend and TSRM to php-src, we've had enough pain with the separation. Let's not mak ethe same mistake again. 3) Let's do /php-src/trunk/ext... php-src/branches/PHP_5_3/ext... to clarify that matter. 4) We should either have 'experimental' next to trunk/tags/branches or we should put experimental stuff into tags. Either way we need to control who can create tags, branches and/or experimental directories. Personally I'd favor an interface that allows select users to create directories under tags that get prefixed by username. E.g. if I used that to create a tree for the re2c lexer rewrite developemnt I'd end up with php-src/tags/helly_re2c_lexer/... 5) No parallel CVS supported integrated into the SVN repository. A gateway that can access SVN Data in a CVS way is nice to have. The easiest way is a cronjob that does snapshots into a readonly CVS repository. Best regards, Marcus