Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Reply-To: <reinhard@apache.org>
From: =?iso-8859-1?Q?Reinhard_P=F6tz?= <reinhard_poetz@gmx.net>
To: <dev@cocoon.apache.org>
Subject: RE: Releasing 2.1
Date: Fri, 1 Aug 2003 11:15:16 +0200
Message-ID: <003201c3580d$6fda6a30$7953efd9@WRPO>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Importance: Normal
In-Reply-To: <LKENJPKDAIKAPKHEOCMMCEKIEHAA.cziegeler@s-und-n.de>


From: Carsten Ziegeler

> I just want to collect opinions how to manage the final release.
> 
> Now, it seems 2.1rc1 is relative stable, no real complains,
> some minor issues but no showstoppers. From that we could 
> say: the current cvs is the final version. point. I don't 
> think we need a rc2.
> 
> Should we take before we do the release some actions? Like...
> ..updating docs ..changing readme ..asking users for testing 
> (which was a success for 2.0.3 and 2.0.4) etc.

IMO there are two important issues:
 
 - the docs must reflect that Cocoon is not a publishing framework
_only_
 - decide what we do with alpha blocks and scratchpad
   I would exclude them from the build properties by default

Cheers,
Reinhard

> 
> Whatever we do, I think a timeframe of two weeks is good, so
> I suggest a final release on tuesday, 12th.
> 
> Carsten
> 
>