cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Turner <>
Subject Re: [VOTE] New CVS Repository Names (was: [PROPOSAL] New CVS Repository Names )
Date Thu, 27 Feb 2003 14:22:01 GMT
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?


> 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

View raw message