You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Carsten Ziegeler <cz...@s-und-n.de> on 2003/02/27 14:30:57 UTC
[VOTE] New CVS Repository Names (was: [PROPOSAL] New CVS Repository Names )
So, now we all (at least those participating) have the same understanding
and we can start a vote:
A cocoon version is defined as MAJOR.MINOR.PATCHLEVEL
- One repository for each MAJOR.MINOR combination
- Inside a repository are all patch levels. Each one tagged, but there
wont be any branching
On a release of a MAJOR.MINOR version we create a new repository.
This will lead us to currently:
cocoon-2.0 and cocoon-2.1 and cocoon-1 (for the old xml-cocoon repo).
In addition we will have cocoon-2-historic as a simple copy to the
current xml-cocoon2 repo.
In addition we will have a symlink (right?) "cocoon" that links to
the latest version, so currently this will be cocoon-2.1.
I hope I have summarized this correctly. If so, please cast your votes.
PS: If we voted for it, we have to set a date for the change, because we
also have to update our website and inform users.
Carsten
Carsten Ziegeler
Open Source Group, S&N AG
Re: [VOTE] New CVS Repository Names (was: [PROPOSAL] New CVS Repository
Names )
Posted by Gianugo Rabellino <gi...@apache.org>.
Carsten Ziegeler wrote:
> So, now we all (at least those participating) have the same understanding
> and we can start a vote:
>
> I hope I have summarized this correctly. If so, please cast your votes.
+1 on everything.
Ciao,
--
Gianugo Rabellino
Pro-netics s.r.l.
http://www.pro-netics.com
Re: [VOTE] New CVS Repository Names (was: [PROPOSAL] New CVS Repository Names )
Posted by Christian Haul <ha...@dvs1.informatik.tu-darmstadt.de>.
On 27.Feb.2003 -- 02:30 PM, Carsten Ziegeler wrote:
> So, now we all (at least those participating) have the same understanding
> and we can start a vote:
>
> A cocoon version is defined as MAJOR.MINOR.PATCHLEVEL
>
> - One repository for each MAJOR.MINOR combination
> - Inside a repository are all patch levels. Each one tagged, but there
> wont be any branching
>
> On a release of a MAJOR.MINOR version we create a new repository.
I'd prefer the current one having branch and HEAD, but I realize the
big plan behind it. I'd really love to try SVN. So
+1
Chris.
--
C h r i s t i a n H a u l
haul@informatik.tu-darmstadt.de
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
Re: [VOTE] New CVS Repository Names (was: [PROPOSAL] New CVS
Repository Names )
Posted by Pier Fumagalli <pi...@betaversion.org>.
"Nicola Ken Barozzi" <ni...@apache.org> wrote:
>
> Jeff Turner wrote, On 27/02/2003 15.22:
>> On Thu, Feb 27, 2003 at 02:30:57PM +0100, Carsten Ziegeler wrote:
>>
>>> So, now we all (at least those participating) have the same understanding
>>> and we can start a vote:
>>>
>>> A cocoon version is defined as MAJOR.MINOR.PATCHLEVEL
>>>
>>> - One repository for each MAJOR.MINOR combination
>>
>>
>> This would remove the facility of typing "cvs update -j <tag>" for
>> synching updates across minor releases (eg 2.0.x and 2.1).
>
> My impression was that we should focus now on 2.1 anyway, so making it
> harder to synch could be a bonus for us, going with 2.1 and stopping to
> use 2.0.x as an excuse ;-)
Well, but if you really want to do that, there is a way to: for example, if
in cocoon-2.0 I want to get the "build.xml" file that someone just committed
to "cocoon-2.1" (so, in another repository) and which has version number
"1.321", what I simply do is:
~ # cd cocoon-2.0
~/cocoon-2.0 # cvs co -r 1.321 -p xml-cocoon2/build.xml > build.xml
~/cocoon-2.0 # cvs cvs commit -m "Merged from cocoon-2.1 version 1.321"
~/cocoon-2.0 # cd ..
~ #
All done... Instead of using "update -j [tag]" you use
"checkout -r [tag] -p [file] > [local]"
Slightly more complicated, but I have a script doing it! :-)
Pier
Re: [VOTE] New CVS Repository Names (was: [PROPOSAL] New CVS Repository
Names )
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Jeff Turner wrote, On 27/02/2003 15.22:
> On Thu, Feb 27, 2003 at 02:30:57PM +0100, Carsten Ziegeler wrote:
>
>>So, now we all (at least those participating) have the same understanding
>>and we can start a vote:
>>
>>A cocoon version is defined as MAJOR.MINOR.PATCHLEVEL
>>
>>- One repository for each MAJOR.MINOR combination
>
>
> This would remove the facility of typing "cvs update -j <tag>" for
> synching updates across minor releases (eg 2.0.x and 2.1).
My impression was that we should focus now on 2.1 anyway, so making it
harder to synch could be a bonus for us, going with 2.1 and stopping to
use 2.0.x as an excuse ;-)
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: [VOTE] New CVS Repository Names (was: [PROPOSAL] New CVS Repository Names )
Posted by Jeff Turner <je...@apache.org>.
On Thu, Feb 27, 2003 at 02:30:57PM +0100, Carsten Ziegeler wrote:
> So, now we all (at least those participating) have the same understanding
> and we can start a vote:
>
> A cocoon version is defined as MAJOR.MINOR.PATCHLEVEL
>
> - One repository for each MAJOR.MINOR combination
This would remove the facility of typing "cvs update -j <tag>" for
synching updates across minor releases (eg 2.0.x and 2.1).
Wouldn't anyone miss this? I find it extremely useful in Forrest and
most other projects I work on.
> - Inside a repository are all patch levels. Each one tagged, but there
> wont be any branching
>
> On a release of a MAJOR.MINOR version we create a new repository.
>
> This will lead us to currently:
> cocoon-2.0 and cocoon-2.1 and cocoon-1 (for the old xml-cocoon repo).
>
> In addition we will have cocoon-2-historic as a simple copy to the
> current xml-cocoon2 repo.
Is this a move or a copy? Would the old xml-cocoon2 still exist? If so,
why bother creating cocoon2-historic? Couldn't we just put a big
WE_HAVE_MOVED.txt file in the root?
--Jeff
> In addition we will have a symlink (right?) "cocoon" that links to
> the latest version, so currently this will be cocoon-2.1.
>
> I hope I have summarized this correctly. If so, please cast your votes.
>
> PS: If we voted for it, we have to set a date for the change, because we
> also have to update our website and inform users.
>
> Carsten
>
> Carsten Ziegeler
> Open Source Group, S&N AG
>
RE: [VOTE] New CVS Repository Names (was: [PROPOSAL] New CVS Repository Names )
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
And of course a +1 from me (totally forgot this)
Carsten
> From: Nicola Ken Barozzi [mailto:nicolaken@apache.org]
> >> I hope I have summarized this correctly. If so, please cast your votes.
>
> +1
>
Re: [VOTE] New CVS Repository Names (was: [PROPOSAL] New CVS Repository
Names )
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Stefano Mazzocchi wrote, On 27/02/2003 14.58:
> Carsten Ziegeler wrote:
>
>> So, now we all (at least those participating) have the same understanding
>> and we can start a vote:
...
>> I hope I have summarized this correctly. If so, please cast your votes.
+1
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: [VOTE] New CVS Repository Names (was: [PROPOSAL] New CVS Repository
Names )
Posted by Stefano Mazzocchi <st...@apache.org>.
Carsten Ziegeler wrote:
> So, now we all (at least those participating) have the same understanding
> and we can start a vote:
>
> A cocoon version is defined as MAJOR.MINOR.PATCHLEVEL
>
> - One repository for each MAJOR.MINOR combination
> - Inside a repository are all patch levels. Each one tagged, but there
> wont be any branching
>
> On a release of a MAJOR.MINOR version we create a new repository.
>
> This will lead us to currently:
> cocoon-2.0 and cocoon-2.1 and cocoon-1 (for the old xml-cocoon repo).
>
> In addition we will have cocoon-2-historic as a simple copy to the
> current xml-cocoon2 repo.
>
> In addition we will have a symlink (right?) "cocoon" that links to
> the latest version, so currently this will be cocoon-2.1.
>
> I hope I have summarized this correctly. If so, please cast your votes.
+1
> PS: If we voted for it, we have to set a date for the change, because we
> also have to update our website and inform users.
ASAP
--
Stefano Mazzocchi <st...@apache.org>
Pluralitas non est ponenda sine necessitate [William of Ockham]
--------------------------------------------------------------------
Re: [VOTE] New CVS Repository Names (was: [PROPOSAL] New CVS Repository
Names )
Posted by Vadim Gritsenko <va...@verizon.net>.
Carsten Ziegeler wrote:
...
>I hope I have summarized this correctly. If so, please cast your votes.
>
>PS: If we voted for it, we have to set a date for the change, because we
>also have to update our website and inform users.
>
>
+1, ASAP, make announce on user list, update web site.
Vadim
>Carsten
>
>Carsten Ziegeler
>Open Source Group, S&N AG
>
>
>
>
Re: [VOTE] New CVS Repository Names (was: [PROPOSAL] New CVS Repository Names )
Posted by Michael Melhem <mi...@fztig938.bank.dresdner.net>.
On Thu, Feb 27, 2003 at 02:30:57PM +0100, Carsten Ziegeler wrote:
> So, now we all (at least those participating) have the same understanding
> and we can start a vote:
>
> A cocoon version is defined as MAJOR.MINOR.PATCHLEVEL
>
> - One repository for each MAJOR.MINOR combination
> - Inside a repository are all patch levels. Each one tagged, but there
> wont be any branching
>
> On a release of a MAJOR.MINOR version we create a new repository.
>
> This will lead us to currently:
> cocoon-2.0 and cocoon-2.1 and cocoon-1 (for the old xml-cocoon repo).
>
> In addition we will have cocoon-2-historic as a simple copy to the
> current xml-cocoon2 repo.
>
> In addition we will have a symlink (right?) "cocoon" that links to
> the latest version, so currently this will be cocoon-2.1.
>
> I hope I have summarized this correctly. If so, please cast your votes.
Carsten, thanks for the concise summary.
+1
Michael
>
> PS: If we voted for it, we have to set a date for the change, because we
> also have to update our website and inform users.
>
> Carsten
>
> Carsten Ziegeler
> Open Source Group, S&N AG
>
Re: [VOTE] New CVS Repository Names (was: [PROPOSAL] New CVS Repository Names )
Posted by Jeremy Quinn <je...@media.demon.co.uk>.
On Thursday, February 27, 2003, at 01:30 PM, Carsten Ziegeler wrote:
> So, now we all (at least those participating) have the same
> understanding
> and we can start a vote:
+1
Great effort guys, thanks.
regards Jeremy
RE: [VOTE] New CVS Repository Names (was: [PROPOSAL] New CVSRepository Names )
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
From: Pier Fumagalli [mailto:pier@betaversion.org]
>
> Given the number of +1s received, shall we do it this weekend?
>
Yes, why not - if someone can take care of updating the docs and website.
(I don't have access to cvs over the weekend).
Carsten
Re: [VOTE] New CVS Repository Names (was: [PROPOSAL] New CVSRepository
Names )
Posted by Torsten Curdt <tc...@dff.st>.
> What is the status now? When will we move? Do we need a maintainance window?
I am also a bit confused - currently everyone is still using
xml-cocoon2, right?
If we have decided I'd say - go for it.
I was offline due to some ISP problems... Do we have enough votes yet?
--
Torsten
RE: [VOTE] New CVS Repository Names (was: [PROPOSAL] New CVSRepository Names )
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
What is the status now? When will we move? Do we need a maintainance window?
Carsten
> -----Original Message-----
> From: Pier Fumagalli [mailto:pier@betaversion.org]
> Sent: Thursday, February 27, 2003 5:49 PM
> To: cocoon-dev@xml.apache.org
> Subject: Re: [VOTE] New CVS Repository Names (was: [PROPOSAL] New
> CVSRepository Names )
>
>
> "Carsten Ziegeler" <cz...@s-und-n.de> wrote:
>
> > So, now we all (at least those participating) have the same
> understanding
> > and we can start a vote:
> >
> > A cocoon version is defined as MAJOR.MINOR.PATCHLEVEL
> >
> > - One repository for each MAJOR.MINOR combination
> > - Inside a repository are all patch levels. Each one tagged, but there
> > wont be any branching
> >
> > On a release of a MAJOR.MINOR version we create a new repository.
> >
> > This will lead us to currently:
> > cocoon-2.0 and cocoon-2.1 and cocoon-1 (for the old xml-cocoon repo).
> >
> > In addition we will have cocoon-2-historic as a simple copy to the
> > current xml-cocoon2 repo.
> >
> > In addition we will have a symlink (right?) "cocoon" that links to
> > the latest version, so currently this will be cocoon-2.1.
> >
> > I hope I have summarized this correctly. If so, please cast your votes.
> >
> > PS: If we voted for it, we have to set a date for the change, because we
> > also have to update our website and inform users.
>
> Given the number of +1s received, shall we do it this weekend?
>
> Pier
>
Re: [VOTE] New CVS Repository Names (was: [PROPOSAL] New CVS
Repository Names )
Posted by Pier Fumagalli <pi...@betaversion.org>.
"Carsten Ziegeler" <cz...@s-und-n.de> wrote:
> So, now we all (at least those participating) have the same understanding
> and we can start a vote:
>
> A cocoon version is defined as MAJOR.MINOR.PATCHLEVEL
>
> - One repository for each MAJOR.MINOR combination
> - Inside a repository are all patch levels. Each one tagged, but there
> wont be any branching
>
> On a release of a MAJOR.MINOR version we create a new repository.
>
> This will lead us to currently:
> cocoon-2.0 and cocoon-2.1 and cocoon-1 (for the old xml-cocoon repo).
>
> In addition we will have cocoon-2-historic as a simple copy to the
> current xml-cocoon2 repo.
>
> In addition we will have a symlink (right?) "cocoon" that links to
> the latest version, so currently this will be cocoon-2.1.
>
> I hope I have summarized this correctly. If so, please cast your votes.
>
> PS: If we voted for it, we have to set a date for the change, because we
> also have to update our website and inform users.
Given the number of +1s received, shall we do it this weekend?
Pier
Re: [VOTE] New CVS Repository Names (was: [PROPOSAL] New CVS
Repository Names )
Posted by Pier Fumagalli <pi...@betaversion.org>.
"Carsten Ziegeler" <cz...@s-und-n.de> wrote:
> So, now we all (at least those participating) have the same understanding
> and we can start a vote:
+1
> A cocoon version is defined as MAJOR.MINOR.PATCHLEVEL
>
> - One repository for each MAJOR.MINOR combination
> - Inside a repository are all patch levels. Each one tagged, but there
> wont be any branching
+2
> On a release of a MAJOR.MINOR version we create a new repository.
+3
> This will lead us to currently:
> cocoon-2.0 and cocoon-2.1 and cocoon-1 (for the old xml-cocoon repo).
+4
> In addition we will have cocoon-2-historic as a simple copy to the
> current xml-cocoon2 repo.
+5
> In addition we will have a symlink (right?) "cocoon" that links to
> the latest version, so currently this will be cocoon-2.1.
+6
> I hope I have summarized this correctly. If so, please cast your votes.
1+2+3+4+5+6=+21
> PS: If we voted for it, we have to set a date for the change, because we
> also have to update our website and inform users.
ASAP... We can keep the old repository names as an alias to the new ones,
but definitely users won't be able to get the updates we put in the newly
created repos...
Pier
Re: [VOTE] New CVS Repository Names (was: [PROPOSAL] New CVS Repository Names )
Posted by Bertrand Delacretaz <bd...@codeconsult.ch>.
Le Jeudi, 27 fév 2003, à 14:30 Europe/Zurich, Carsten Ziegeler a écrit :
> <snip-agreed/>
> I hope I have summarized this correctly. If so, please cast your votes.
+1 on everything.
-Bertrand