Return-Path: 
 <cocoon-dev-return-37400-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 25356 invoked by uid 500); 27 Feb 2003 11:51:09 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 25337 invoked from network); 27 Feb 2003 11:51:07 -0000
Received: from unknown (HELO mailhost.experian.co.uk) (194.60.170.33)
  by daedalus.apache.org with SMTP; 27 Feb 2003 11:51:07 -0000
Received: from exchukthin01.experian.co.uk (unverified) by
 mailhost.experian.co.uk
 (Content Technologies SMTPRS 4.1.2) with ESMTP id
 <Tc23caa2160ab89a583@mailhost.experian.co.uk> for
 <cocoon-dev@xml.apache.org>;
 Thu, 27 Feb 2003 11:53:05 +0000
Received: by exchukthin01.experian.co.uk with Internet Mail Service
 (5.5.2653.19)
	id <1NLTDM13>; Thu, 27 Feb 2003 11:46:39 -0000
Message-ID: 
 <CCD084B0E779D411A70300508B66222605A32D57@exchukahis02.experian.co.uk>
From: "Morrison, John" <John.Morrison@uk.experian.com>
To: "'cocoon-dev@xml.apache.org'" <cocoon-dev@xml.apache.org>
Subject: RE: [PROPOSAL] New CVS Repository Names (Was: Re: [proposal] Prun
	ing up the CVS tree for real)
Date: Thu, 27 Feb 2003 11:46:39 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

> From: Gianugo Rabellino [mailto:gianugo@apache.org]

<snip agreed/>

> > - Create a new repository called "cocoon-2.1" and copy over 
> head from the
> >   main "xml-cocoon2" repository (clean checkout, and re-import)
> >     (this has been created as a part of this proposal, and 
> it contains what
> >     it should. All files are down at version 1.1 in this repository)
> 
> Here I'm not sure. ATM I'd rather have the latest cocoon version in a 
> repository such as plain "cocoon" (think CVS HEAD). In this Cocoon 
> lifecycle it represents 2.1. When we release 2.1, we can move 
> this repo 
> to cocoon-2.1 and start using it (with tagging, no branching) 
> for 2.1.x 
> releases, while "cocoon" would become the 2.2 repo. Isn't it cleaner 
> from a logical POV?

This I prefer.  A version'd cvs is created when it gets released.

J.


=======================================================================
Information in this email and any attachments are confidential, and may
not be copied or used by anyone other than the addressee, nor disclosed
to any third party without our permission.  There is no intention to
create any legally binding contract or other commitment through the use
of this email.

Experian Limited (registration number 653331).  
Registered office: Talbot House, Talbot Street, Nottingham NG1 5HF