Re: 2.7.3 release plan

Others and I committed a few, I pushed out a few. Down to just three now! +Vinod > On Apr 6, 2016, at 3:00 PM, Vinod Kumar Vavilapalli > wrote: > > Down to only 10 blocker / critical tickets > (https://issues.apache.org/jira/issues/?filter=12335343 >

Re: 2.7.3 release plan

rg>; hdfs-...@hadoop.apache.org; mapreduce-dev@hadoop.apache.org Sent: Wednesday, April 6, 2016 5:00 PM Subject: Re: 2.7.3 release plan Down to only 10 blocker / critical tickets (https://issues.apache.org/jira/issues/?filter=12335343 <https://issues.apache.org/jira/issues/?filter

Re: 2.7.3 release plan

Down to only 10 blocker / critical tickets (https://issues.apache.org/jira/issues/?filter=12335343 ) now! Thanks +Vinod > On Mar 30, 2016, at 4:18 PM, Vinod Kumar Vavilapalli > wrote: > > Hi all, > > Got nudged

Re: 2.7.3 release plan

Allen, I see you marked it for 2.7.3, so it’s there on my radar. That said, I’ll definitely need help from you (and likely others) in getting it fixed. Thanks +Vinod > On Apr 6, 2016, at 2:13 PM, Allen Wittenauer > wrote: > > > This is probably a

Re: 2.7.3 release plan

gt;>>> operational path for rolling downgrade. >>>>>>> >>>>>>> On Thu, Mar 31, 2016 at 10:10 AM, Junping Du <j...@hortonworks.com> >>>>> wrote: >>>>>>>> Thanks for bringing up this topic, Sean. >>&

Re: 2.7.3 release plan

This is probably a good time to remind/point folks to HADOOP-12893. Apache Hadoop's binary artifacts (with or without native code) and source artifacts are not complying with the licenses of bundled components. I fairly confident this means releases are off the table until someone

Re: 2.7.3 release plan

t; > >>>>> > > >>>>> I agree that this fix is important, I just think we should either > cut > > >>>>> a version of 2.8 that includes it or find a way to do it that gives > > an > > >>>>> operational path for rolling downgrade. > > >>>>>

Re: 2.7.3 release plan

gt;> HDFS-8791 > >>>>> haven't been committed in so that's why we didn't discuss this > >> earlier. > >>>>>> I remember in JIRA discussion, we treated this layout change as a > >>>>> Blocker bug that fixing a significant performance r

Re: 2.7.3 release plan

ommunity already >>> did >>>>> their best with careful and patient to deliver the fix and other >> related >>>>> patches (like upgrade fix in HDFS-8578). Take an example of HDFS-8578, >>> you >>>>> can see 30+ rounds patch review

Re: 2.7.3 release plan

dy >> > did >> > >> their best with careful and patient to deliver the fix and other >> related >> > >> patches (like upgrade fix in HDFS-8578). Take an example of HDFS-8578, >> > you >> > >> can see 30+ rounds patch review back and forth by

Re: 2.7.3 release plan

t;> their best with careful and patient to deliver the fix and other >> related >> > >> patches (like upgrade fix in HDFS-8578). Take an example of HDFS-8578, >> > you >> > >> can see 30+ rounds patch review back and forth by senior c

Re: 2.7.3 release plan

gt; not to > > >> mention the outstanding performance test data in HDFS-8791. > > >> > I would trust our HDFS committers' judgement to land HDFS-8791 on > > >> 2.7.3. However, that needs Vinod's final confirmation who serves as RM > > for > > >> bra

Re: 2.7.3 release plan

mation who serves as RM > for > >> branch-2.7. In addition, I didn't see any blocker issue to bring it into > >> 2.6.5 now. > >> > Just my 2 cents. > >> > > >> > Thanks, > >> > > >> > Junping > >> > > >> >

Re: 2.7.3 release plan

inod's final confirmation who serves as RM for >> branch-2.7. In addition, I didn't see any blocker issue to bring it into >> 2.6.5 now. >> > Just my 2 cents. >> > >> > Thanks, >> > >> > Junping >> > >> > __

Re: 2.7.3 release plan

gt; Junping > > > > > > From: Sean Busbey <bus...@cloudera.com> > > Sent: Thursday, March 31, 2016 2:57 PM > > To: hdfs-...@hadoop.apache.org > > Cc: Hadoop Common; yarn-...@hadoop.apache.org; > mapreduce-dev@hado

Re: 2.7.3 release plan

...@hadoop.apache.org > Cc: Hadoop Common; yarn-...@hadoop.apache.org; mapreduce-dev@hadoop.apache.org > Subject: Re: 2.7.3 release plan > > A layout change in a maintenance release sounds very risky. I saw some > discussion on the JIRA about those risks, but the consensus seemed to > be &

Re: 2.7.3 release plan

ct: Re: 2.7.3 release plan A layout change in a maintenance release sounds very risky. I saw some discussion on the JIRA about those risks, but the consensus seemed to be "we'll leave it up to the 2.6 and 2.7 release managers." I thought we did RMs per release rather than per branch?

Re: 2.7.3 release plan

A layout change in a maintenance release sounds very risky. I saw some discussion on the JIRA about those risks, but the consensus seemed to be "we'll leave it up to the 2.6 and 2.7 release managers." I thought we did RMs per release rather than per branch? No one claiming to be a release manager

Re: 2.7.3 release plan

Thank you Vinod! FYI: 2.7.3 will be a bit special release. HDFS-8791 bumped up the datanode layout version, so rolling downgrade from 2.7.3 to 2.7.[0-2] is impossible. We can rollback instead. https://issues.apache.org/jira/browse/HDFS-8791

2.7.3 release plan

Hi all, Got nudged about 2.7.3. Was previously waiting for 2.6.4 to go out (which did go out mid February). Got a little busy since. Following up the 2.7.2 maintenance release, we should work towards a 2.7.3. The focus obviously is to have blocker issues [1], bug-fixes and *no* features /