perl-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philippe M. Chiasson" <go...@ectoplasm.org>
Subject [Discuss] The various possible SVN layouts
Date Sun, 21 Nov 2004 23:05:25 GMT
As was raised in a previous discussion, there are many ways that the 
modperl svn repository could be structured.

Currently, it stands like :

modperl-current (aka 2.0)
Codebase:     [svn]/perl/modperl/trunk
Release tags: [svn]/perl/modperl/tags
Branches:      [svn]/perl/modperl/branches

Docs:
Codebase:     [svn]/perl/modperl/docs/trunk
Release tags: [svn]/perl/modperl/docs/tags
Branches:      [svn]/perl/modperl/docs/branches

modperl-1.0 (proposed)
Codebase:     [svn]/perl/modperl/branches/1.x
Release tags: [svn]/perl/modperl/tags
Branches:      [svn]/perl/modperl/branches

embperl-2.0 (proposed)
Codebase:     [svn]/perl/embperl/trunk
Release tags: [svn]/perl/embperl/tags
Branches:      [svn]/perl/embperl/branches

embperl-1.0 (proposed)
Codebase:     [svn]/perl/embperl/branches/1.x
Release tags: [svn]/perl/embperl/tags
Branches:      [svn]/perl/embperl/branches

Another different layout proposed so far was :

modperl-current (aka 2.0)
Codebase:      [svn]/perl/modperl-2.0/trunk
Release tags:  [svn]/perl/modperl-2.0/tags
Branches:       [svn]/perl/modperl-2.0/branches

docs:
Codebase:      [svn]/perl/modperl-docs/trunk
Release tags:  [svn]/perl/modperl-docs/tags
Branches:       [svn]/perl/modperl-docs/branches

modperl-1.0:
Codebase:      [svn]/perl/modperl-1.0/trunk
Release tags:  [svn]/perl/modperl-1.0/tags
Branches:       [svn]/perl/modperl-1.0/branches

embperl-1.0:
Codebase:      [svn]/perl/embperl-1.0/trunk
Release tags:  [svn]/perl/embperl-1.0/tags
Branches:       [svn]/perl/embperl-1.0/branches

embperl-2.0:
Codebase:      [svn]/perl/embperl-2.0/trunk
Release tags:  [svn]/perl/embperl-2.0/tags
Branches:       [svn]/perl/embperl-2.0/branches

I am sure there are many more possibly layouts as valid not illustrated 
here.

So, I'd like to know what people think are positive vs. negative points 
in these 2 different approaches. Keep in mind
that having full control to move stuff in subversion without having to 
pay the price CVS would have costed, we have
a lot of freedom here.

Once we can decide/vote on a layout that works for all, I'll be more 
than happy to take care of the moving operations.

Gozer out.


Mime
View raw message