[Proposal] svn dirs reorganization

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[Proposal] svn dirs reorganization

vmassol
Administrator
Hi,

Following my post entitled "[Proposal] Plugins and xwiki distributions" I'd
like to propose that we reorganize our SVN. Here's what I propose:

xwiki/
  |_ xwiki/
    |_ trunks/
    |_ branches/
    |_ tags/
  |_ xwiki-plugins/
    |_ trunks/
      |_ emailnotification/
      |_ lucene/
      |_ ...
    |_ branches/
    |_ tags/
  |_ xwiki-apps/
    |_ trunks/
    |_ branches/
    |_ tags/
  |_ xwiki-clients/
    |_ trunks/
    |_ branches/
    |_ tags/
  |_ xwiki-sandbox/
    |_ trunks/
    |_ branches/
    |_ tags/
  |_ xwiki-tools/
    |_ trunks/
    |_ branches/
    |_ tags/

The rationale:

* It's really cumbersome to have trunks/, tags/ and branches/ for each
single module. It's easier and better to have only one per category (xwiki,
xwiki-apps, xwiki-clients, etc). Of course each project inside these can
still release in its own lifecycle and tag independently. For example check
the plugins/tags/ dir for Maven
(https://svn.apache.org/repos/asf/maven/plugins/tags/) and you'll see that
each plugin is released separately.

* Having trunks/ at different levels doesn't sound like a good idea.
Actually I discovered this when trying to create svn:externals for all
trunks. The same would happen if you tried to check out all the trunks
manually. You would currently get some directories that are not under
version control (xwiki-plugins/, xwiki-clients/, etc). The reason is that
there's no way to check the contents of these directories by taking only the
trunks and still having them under svn control.

Thus my belief is that trunks/ dir at different directory levels in a SVN
directory is not a good idea if everything is in the same project.

Again a good structure is shown by Maven:
https://svn.apache.org/repos/asf/maven/ (all the trunks/ are at the same
level)

* Last, we have a gelc/gelcv1 dir. I don't think we should put version in
the directory structure but rather use trunks and branches for this. I think
it'd be better to use the trunk for v1 and when a v2 comes out, move the v1
to a branch and the v2 to the trunk.

I'd like to reorganize the svn tree to follow what I've defined above. Let
me know if you're ok for me to do it. As some of you might have some
uncommitted changes in your local repo let me know if I can do it. I'd like
to start with the xwiki-plugins/ tree.



Thanks
-Vincent


       

       
               
___________________________________________________________________________
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
Demandez à ceux qui savent sur Yahoo! Questions/Réponses
http://fr.answers.yahoo.com



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

RE: [Proposal] svn dirs reorganization

vmassol
Administrator
Update: I've just done this for xwiki-plugins to try it out. Let me know if
it's an issuer for anyone and I'll revert it.

Please let me know also whether you're ok to do it for the rest too.



Thanks
-Vincent

> -----Original Message-----
> From: Vincent Massol [mailto:[hidden email]]
> Sent: samedi 21 octobre 2006 10:13
> To: [hidden email]
> Subject: [xwiki-dev] [Proposal] svn dirs reorganization
>
> Hi,
>
> Following my post entitled "[Proposal] Plugins and xwiki distributions"
> I'd like to propose that we reorganize our SVN. Here's what I propose:
>
> xwiki/
>   |_ xwiki/
>     |_ trunks/
>     |_ branches/
>     |_ tags/
>   |_ xwiki-plugins/
>     |_ trunks/
>       |_ emailnotification/
>       |_ lucene/
>       |_ ...
>     |_ branches/
>     |_ tags/
>   |_ xwiki-apps/
>     |_ trunks/
>     |_ branches/
>     |_ tags/
>   |_ xwiki-clients/
>     |_ trunks/
>     |_ branches/
>     |_ tags/
>   |_ xwiki-sandbox/
>     |_ trunks/
>     |_ branches/
>     |_ tags/
>   |_ xwiki-tools/
>     |_ trunks/
>     |_ branches/
>     |_ tags/
>
> The rationale:
>
> * It's really cumbersome to have trunks/, tags/ and branches/ for each
> single module. It's easier and better to have only one per category
> (xwiki, xwiki-apps, xwiki-clients, etc). Of course each project inside
> these can still release in its own lifecycle and tag independently. For
> example check the plugins/tags/ dir for Maven
> (https://svn.apache.org/repos/asf/maven/plugins/tags/) and you'll see
> that each plugin is released separately.
>
> * Having trunks/ at different levels doesn't sound like a good idea.
> Actually I discovered this when trying to create svn:externals for all
> trunks. The same would happen if you tried to check out all the trunks
> manually. You would currently get some directories that are not under
> version control (xwiki-plugins/, xwiki-clients/, etc). The reason is
> that there's no way to check the contents of these directories by
> taking only the trunks and still having them under svn control.
>
> Thus my belief is that trunks/ dir at different directory levels in a
> SVN directory is not a good idea if everything is in the same project.
>
> Again a good structure is shown by Maven:
> https://svn.apache.org/repos/asf/maven/ (all the trunks/ are at the
> same
> level)
>
> * Last, we have a gelc/gelcv1 dir. I don't think we should put version
> in the directory structure but rather use trunks and branches for this.
> I think it'd be better to use the trunk for v1 and when a v2 comes out,
> move the v1 to a branch and the v2 to the trunk.
>
> I'd like to reorganize the svn tree to follow what I've defined above.
> Let me know if you're ok for me to do it. As some of you might have
> some uncommitted changes in your local repo let me know if I can do it.
> I'd like to start with the xwiki-plugins/ tree.
>
>
>
> Thanks
> -Vincent
>
>
>
>
>
>
> _______________________________________________________________________
> ____
> Dicouvrez une nouvelle fagon d'obtenir des riponses ` toutes vos
> questions !
> Demandez ` ceux qui savent sur Yahoo! Questions/Riponses
> http://fr.answers.yahoo.com


       

       
               
___________________________________________________________________________
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
Demandez à ceux qui savent sur Yahoo! Questions/Réponses
http://fr.answers.yahoo.com



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws