geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hernan Cunico <>
Subject Re: Release Early, Release Often
Date Fri, 08 Sep 2006 14:00:38 GMT
For Geronimo v1.1 we gathered a list with the user requirements and made 
it available in the wiki.

I would propose we do the same for the next release (v1.2 for now) and 
include, along with the user requirements, the features we would like to 
have. Yup, that's the roadmap we are all talking about.

Here is a template based on what we had for v1.1

If we want to release early/often then we could add a tentative target 
date per feature, not necessarily release, just feature added to trunk.

I know adding dates is not too appealing but if we want to deliver often 
  on regular basis we need to somehow time-box the releases.

There is already a discussion about uncertified weekly builds but, how 
often do we want to deliver a fully certified release?

We already have some "structure" for monitoring (or better trying to 
monitor) the project development status

Any ideas how we could reuse this info/templates?

Would it be better to have the "Apache Geronimo Development Status" 
moved under "Apache Geronimo Development"?

What would help us to stay on track


Bruce Snyder wrote:
> On 9/7/06, Hiram Chirino <> wrote:
>> I'm a big believer that 1.3 will have a ton of nice features!  If you
>> release it, users will use it :)  I don't think we need to feature
>> pack every release.
>> It seems to me we spent a bunch of time feature packing a 1.1.x
>> release.  If we would do that to trunk instead, our 1.n releases would
>> be more impressive.
> Agreed - forward progress and a visible roadmap are what users want to
> see. Right now Geronimo is headed pretty squarely down the path of
> updates every six months. IMO, we need to change that and feature
> packing every release is only going to keep things on that track.
> Bruce

View raw message