It seems that the Nigel's previous suggestion (i.e. append Sept 18, others Sept 4) is better.
For your reference, attached the previous message thread "[VOTE] Push back code freeze for 0.21" at the end . Nicholas Sze ----- Original Message ---- > From: Nigel Daley <nda...@yahoo-inc.com> > To: common-dev@hadoop.apache.org > Sent: Thursday, August 13, 2009 2:23:24 PM > Subject: Re: [VOTE] Freeze date for Common, HDFS, and MapReduce 0.21 > > +1 > On Aug 12, 2009, at 4:04 PM, Owen O'Malley wrote: > > > All, > > After the discussion settled last time, it seems that HDFS needs more > > time > to settle append and sync. Therefore, I'd like to propose a freeze time of > 4:30 > pst on 18 Sep for making the 0.21 branch for Common, HDFS, and MapReduce. > > > > -- Owen > From: Eric Baldeschwieler <eri...@yahoo-inc.com> > To: common-dev@hadoop.apache.org > Sent: Friday, July 24, 2009 5:11:15 PM > Subject: Re: [VOTE] Push back code freeze for 0.21 > > AGGHH! > > Let's not push out the general freeze even as far as sept 4th if > possible. I'd suggest oct 31st. If we push out the general freeze > until append is complete, we will delay having a stable release with > append at least an additional month. > > E14 > > > > > From: Nigel Daley > > Date: Fri, 24 Jul 2009 16:30:55 -0700 > > To: > > Subject: Re: [VOTE] Push back code freeze for 0.21 > > > > > > There's a 3rd option I'd support. Feature freeze on Sept 4, except > > for Append which gets a 2 week extension. This allows us to start > > stabilizing the rest of the code base while Append is finished up. > > > > Nige > > > > On Jul 24, 2009, at 4:25 PM, Konstantin Boudnik wrote: > > > > > I second Konstantin's point: FI tests are likely to take a pretty > > > hefty chunk of overall dev. time. Considering that people'd be > > > facing a certain learning curve to master this new technology we are > > > likely to need more time for the completion of the development of > > > the code & tests. > > > > > > +1 for farther push back, e.g. until 9/18/09 > > > > > > Konstantin (aka Cos) > > > > > > On 7/24/09 4:18 PM, Konstantin Shvachko wrote: > > >> I would like to clarify the append plans. > > >> Right now according to our planning schedule we need about > > >> 8 weeks to complete the implementation of the design. > > >> This will include all the functionality and unit testing > > >> according to the test plan. > > >> > > >> September 4 deadline gives us about 6 weeks to commit the features. > > >> Which is 2 weeks short off our schedule. > > >> This of course if the implementation will not go much faster than > > >> we predicted :-). > > >> > > >> So, we can either move the freeze a couple of weeks further ahead. > > >> Or we can also use some help from the people familiar with the > > >> design. > > >> E.g. there is a lot of hours scheduled to unit test writing using > > >> fault > > >> injection, etc. > > >> > > >> Thanks, > > >> --Konstantin > > >> > > >> Amr Awadallah wrote: > > >>> +1 for stable append. > > >>> > > >>> -- amr > > >>> > > >>> Dhruba Borthakur wrote: > > >>>> +1 > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> On 7/24/09, Jim Kellerman > > >>>> (POWERSET) wrote: > > >>>> > > >>>>> +1 > > >>>>> > > >>>>> > > >>>>>> -----Original Message----- > > >>>>>> From: Owen O'Malley [mailto:omal...@apache.org] > > >>>>>> Sent: Friday, July 24, 2009 1:11 PM > > >>>>>> To: common-dev@hadoop.apache.org > > >>>>>> Subject: [VOTE] Push back code freeze for 0.21 > > >>>>>> > > >>>>>> I'd like to push the date for the code freeze back to 4 > > >>>>>> September to > > >>>>>> give the file append more time to be finished well. Clearly, > > >>>>>> I'm +1. > > >>>>>> > > >>>>>> -- Owen > > >>>>>> > > >>>>> > > >>>> > > > > > > -- > > > With best regards, > > > Konstantin Boudnik (aka Cos) > > > > > > Yahoo! Grid Computing > > > +1 (408) 349-4049 > > > > > > 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 > > > Attention! Streams of consciousness are disallowed > > > > > > > > > > > ------ End of Forwarded Message ----- Original Message ----
