+1 on Arvind as 1.1.0 RM and on a 1.1.0 branch. +0 on labeling the release beta. Kind of feel like it's something to list in the README (on advice from phunt) and just release. Otherwise, it sounds like there will be a 1.1.0 final (which the ASF doesn't do). The advice I got when we tackled this with 1.0.0 was that the ASF produces releases, period. The quality can be indicated in the README (unless I misunderstood).
Thanks for volunteering, Arvind! On Tue, Mar 13, 2012 at 9:29 AM, Arvind Prabhakar <[email protected]> wrote: > On Tue, Mar 13, 2012 at 7:53 AM, Ralph Goers <[email protected]> > wrote: > > > > On Mar 12, 2012, at 10:59 PM, Juhani Connolly wrote: > >>>> > >>> > >> While we have added some cool new features, and fixed some bugs, other > new ones have appeared and some of the sub-tasks of the original flume-728 > task have been left by the wayside. We're talking about putting 1.1.0 out > but there's no target for what 1.1.0 is meant to have? I hope we're not > heading towards a development style of "release whatever we've done" > without a plan. > > > > Software is never perfect. Apache philosophy has always been that it is > better to release often than constantly be waiting for features or specific > bug fixes - unless they are determined to be blockers. Users really like > getting their hands on the software without having to build it. > > > > While I think roadmaps are great as a discussion point, the proof of > what is needed is what the developers actually write and commit. It doesn't > make sense to wait for something on the roadmap that no one really wants to > implement or that users are OK with living without. > > > > That said, every attempt should be made to release software that does > what it says it does and is reliable. That is why I asked the question > about the version number. A release with just a number carries certain > expectations that a release with "beta" in it doesn't have. > > I agree with Ralph's point here. We have had a 1.0.0 alpha release and > what we release right now is going to be more of a beta than anything > else. Primarily because of all the reasons Juhani pointed out - this > release will leave room for improvement. > > +1 on officially labeling 1.1.0-incubating version as a "beta". > > We can continue to have the roadmap discussion and work out the plan > for delivering the in-flight features in 1.2.0 which will should > target to make a stable release. > > Thanks, > Arvind Prabhakar > > > > > > Ralph > -- Eric Sammer twitter: esammer data: www.cloudera.com
