You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ecs-dev@jakarta.apache.org by Henri Yandell <fl...@gmail.com> on 2005/02/25 06:27:08 UTC
SVN strategy
ECS is largely quite simple with regards to its repository structure;
the only issue to figure out is the unreleased jakarta-ecs2 version.
It seems to me we should:
move jakarta-ecs to:
jakarta/
ecs/
tags/
branches/
trunk/ (jakarta-ecs HEAD)
and then optionally keep the jakarta-ecs2 module as
jakarta/ecs/branches/ecs2 or jakarta/ecs/newversion or something.
Any +1's/-1's for the general approach, and any ideas on the ecs2 handling?
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: ecs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: ecs-dev-help@jakarta.apache.org
Re: SVN strategy
Posted by Henri Yandell <fl...@gmail.com>.
So all in favour for:
*************************
We need to export
jakarta-ecs
to SVN and then lock the CVS module.
The resulting repo we need is:
/jakarta/
/ecs/
/branches/ (jakarta-ecs branches)
/tags/ (jakarta-ecs tags)
/trunk/ (jakarta-ecs HEAD)
We would then like jakarta-ecs2 to be migrated to:
/jakarta/
/ecs/
/branches/
/ecs2 (jakarta-ecs2 HEAD)
*********************
Looking at ecs2, there don't seem to be any important tags or branches
that we'd be worried about losing.
I'll send this through to Infra on Wednesday if I don't hear otherwise :)
Hen
On Sat, 26 Feb 2005 18:03:35 +0000, robert burrell donkin
<ro...@blueyonder.co.uk> wrote:
> +1
>
> just for neatness i'd be inclined to keep it around in branches/ecs2.
>
> - robert
>
> On Sat, 2005-02-26 at 02:55, snagy wrote:
> > +1 from me; due to the lack of interest in ecs2 and the inactivity in
> > general I don't know that it's necessary to keep it around at all.
> >
> > -stephan
> >
> > Henri Yandell wrote:
> >
> > >ECS is largely quite simple with regards to its repository structure;
> > >the only issue to figure out is the unreleased jakarta-ecs2 version.
> > >
> > >It seems to me we should:
> > >
> > >move jakarta-ecs to:
> > >
> > >jakarta/
> > > ecs/
> > > tags/
> > > branches/
> > > trunk/ (jakarta-ecs HEAD)
> > >
> > >and then optionally keep the jakarta-ecs2 module as
> > >jakarta/ecs/branches/ecs2 or jakarta/ecs/newversion or something.
> > >
> > >Any +1's/-1's for the general approach, and any ideas on the ecs2 handling?
> > >
> > >Hen
> > >
> > >---------------------------------------------------------------------
> > >To unsubscribe, e-mail: ecs-dev-unsubscribe@jakarta.apache.org
> > >For additional commands, e-mail: ecs-dev-help@jakarta.apache.org
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ecs-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: ecs-dev-help@jakarta.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ecs-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: ecs-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ecs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: ecs-dev-help@jakarta.apache.org
Re: SVN strategy
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
+1
just for neatness i'd be inclined to keep it around in branches/ecs2.
- robert
On Sat, 2005-02-26 at 02:55, snagy wrote:
> +1 from me; due to the lack of interest in ecs2 and the inactivity in
> general I don't know that it's necessary to keep it around at all.
>
> -stephan
>
> Henri Yandell wrote:
>
> >ECS is largely quite simple with regards to its repository structure;
> >the only issue to figure out is the unreleased jakarta-ecs2 version.
> >
> >It seems to me we should:
> >
> >move jakarta-ecs to:
> >
> >jakarta/
> > ecs/
> > tags/
> > branches/
> > trunk/ (jakarta-ecs HEAD)
> >
> >and then optionally keep the jakarta-ecs2 module as
> >jakarta/ecs/branches/ecs2 or jakarta/ecs/newversion or something.
> >
> >Any +1's/-1's for the general approach, and any ideas on the ecs2 handling?
> >
> >Hen
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: ecs-dev-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: ecs-dev-help@jakarta.apache.org
> >
> >
> >
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ecs-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: ecs-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ecs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: ecs-dev-help@jakarta.apache.org
Re: SVN strategy
Posted by snagy <sn...@sbcglobal.net>.
+1 from me; due to the lack of interest in ecs2 and the inactivity in
general I don't know that it's necessary to keep it around at all.
-stephan
Henri Yandell wrote:
>ECS is largely quite simple with regards to its repository structure;
>the only issue to figure out is the unreleased jakarta-ecs2 version.
>
>It seems to me we should:
>
>move jakarta-ecs to:
>
>jakarta/
> ecs/
> tags/
> branches/
> trunk/ (jakarta-ecs HEAD)
>
>and then optionally keep the jakarta-ecs2 module as
>jakarta/ecs/branches/ecs2 or jakarta/ecs/newversion or something.
>
>Any +1's/-1's for the general approach, and any ideas on the ecs2 handling?
>
>Hen
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: ecs-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: ecs-dev-help@jakarta.apache.org
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ecs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: ecs-dev-help@jakarta.apache.org