+1 (non-binding) to stabilize 2.0, and add new features only after a stable release. I understand that what constitutes as "new feature" versus "stabilizing" is subjective.
Thanks, Joep On May 1, 2013, at 12:53 PM, Konstantin Shvachko wrote: > > > Please vote on the following plan for Hadoop release 2.0.5 > > - bug fixes encountered in current release 2.0.4-alpha > > - make all API changes to allow freezing them post 2.0.5 > > - no new features > > > > As discussed on @dev thread > > http://s.apache.org/fs > > this will allow to stabilize 2.0 branch in a short and predictable period > > of time. > > This enables a powerful option to have the release tested at Yahoo scale. > > The plan is to follow up with 2.1.0 - the stable release. > > New features can and should be added on top of the stable release once it > > is out. > > > > Hadoop by-laws: > > http://hadoop.apache.org/bylaws.html > > > > "Release Plan > > Defines the timetable and actions for a release. The plan also nominates > a > > Release Manager. > > Lazy majority of active committers" > > > > assume nomination of a Release Manager with the plan. > > It would be really good if Arun continues if this plan is adopted. > > We can return to the RM topic if not. > > > > The vote will run for 7 days until next Wed, May 8th. > > > > Thanks, > > --Konstantin > >
