Return-Path: 
 <forrest-dev-return-3412-apmail-xml-forrest-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org
Received: (qmail 65590 invoked by uid 500); 12 Nov 2002 09:53:33 -0000
Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:forrest-dev-help@xml.apache.org>
list-unsubscribe: <mailto:forrest-dev-unsubscribe@xml.apache.org>
list-post: <mailto:forrest-dev@xml.apache.org>
Reply-To: forrest-dev@xml.apache.org
Delivered-To: mailing list forrest-dev@xml.apache.org
Received: (qmail 65581 invoked from network); 12 Nov 2002 09:53:32 -0000
Received: from fep01.tuttopmi.it (HELO fep01-svc.flexmail.it)
 (212.131.248.100)
  by daedalus.apache.org with SMTP; 12 Nov 2002 09:53:32 -0000
Received: from apache.org ([80.204.154.181]) by fep01-svc.flexmail.it
          (InterMail vM.5.01.05.09 201-253-122-126-109-20020611) with ESMTP
          id <20021112095343.SRPF1512.fep01-svc.flexmail.it@apache.org>
          for <forrest-dev@xml.apache.org>; Tue, 12 Nov 2002 10:53:43 +0100
Message-ID: <3DD0CF5C.4060709@apache.org>
Date: Tue, 12 Nov 2002 10:52:28 +0100
From: Nicola Ken Barozzi <nicolaken@apache.org>
Reply-To: nicolaken@apache.org
Organization: Apache Software Foundation
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: forrest-dev@xml.apache.org
Subject: Re: [VOTE] Forrest 0.2 release
References: <20021112092811.GC6712@expresso.localdomain>
 <3DD0CDB1.4090401@outerthought.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N


Steven Noels wrote:
> Jeff Turner wrote:
> 
>> Second try :)
>>
>> While Nicola and I try to whack ideas into each others heads, I think we
>> really do need a release before both of us commit a bunch of new
>> features.
>>
>> So I propose we:
>>
>>  - Write a minimal Tomcat-style etc/RELEASE-NOTES-0.2.txt mentioning open
>>    bugs.
>>  - tag current CVS as 'FORREST_02', but excluding the contentious patch
>>  - generate source and binary distributions (incl. release notes in root)
>>    and put them somewhere public.
>>  - draft a minimal email announcing the release, review it here on
>>    forrest-dev, then send to general@ and announce@
> 
> 
> While releasing is good, I'm not so sure whether we have the right 
> motivation to do so right now.
> 
> A lot of the stuff isn't finished (the Wiki stuff & DTDs basically), nor 
> can we offer a binding contract / migration path to our users IMHO.

It's a 0.x release, and OS projectrs are never finished ;-)

> If you want to tag for easier bookkeeping - please go ahead. Internal 
> release, without announce mails: +1

I'd make an announcement, but clearly state that it's not a final one, 
just to help users try out Forrest's features with a release as they 
have requested.

> But all in all, I think we need to stabilize and package before we can 
> publicly release. Remember there is no second chance for a first 
> impression.
> 
> And as you all know, we will have time, energy & focus to work on 
> Forrest for 6 weeks full-time after the GetTogether. Part of that time 
> can go to updating & solidifying documentation, and testing the new 
> additions.
> 
> (oh my god, I'm gonna be flamed for this - but the 0.1 release mail has 
> been sitting in my draft folder since 2002/07/16, honestly)
> 
> (I haven't cast my vote yet)
> 
> </Steven>

Let's just do a quick release with just "technical" announcement, 
especially to the projects like incubator and commons that are starting 
to use it.

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------