Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: forrest-dev@xml.apache.org
Date: Tue, 2 Sep 2003 10:17:58 -0400 (EDT)
From: Dave Brondsema <dave@brondsema.net>
To: forrest-dev@xml.apache.org
Subject: Re: Fixed release dates (was Re: About Integrate Forrest Maven plugin
  (FOR-55))
In-Reply-To: <bj277q$fp2$1@sea.gmane.org>
Message-ID: 
 <Pine.LNX.4.44L0.0309021014390.10705-100000@delorean.solidusdesign.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Tue, 2 Sep 2003, Nicola Ken Barozzi wrote:
>
> Juan Jose Pablos wrote, On 02/09/2003 15.19:
> > Hi List,
> >
> > Do we want to add this before the release?
>
> I'd say that the person doing the release should decide when he has good
> time to do it. Then, we decide a freeze date some days before it, and
> everything that is committed before becomes part of the release.
>
> This is because IMHO timed releases are better for a project like
> Forrest that has so many extra features in it.
>
> Jeff, if you are still willing to do the release, please tell us when
> and give us a freeze date, so that whoever wants to add other things
> shall do so before that date.
>
> Also, what about setting other fixed release dates? How about one every
> two months?
>
> --
> Nicola Ken Barozzi                   nicolaken@apache.org
>              - verba volant, scripta manent -
>     (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
>

What about releases based on certain features?  For example, say 0.6 will
have a redesigned directory structure.  Or is forrest development still
too active/changing/young to constrain it to a certain roadmap?

Dave Brondsema