Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
User-Agent: Microsoft-Entourage/10.1.1.2418
Date: Thu, 27 Feb 2003 14:04:22 +0000
Subject: Re: [VOTE] New CVS Repository Names (was: [PROPOSAL] New CVS
	Repository Names )
From: Pier Fumagalli <pier@betaversion.org>
To: <cocoon-dev@xml.apache.org>
Message-ID: <BA83CB66.C65F%pier@betaversion.org>
In-Reply-To: <LKENJPKDAIKAPKHEOCMMMEFDCNAA.cziegeler@s-und-n.de>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit

"Carsten Ziegeler" <cziegeler@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