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

-...@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=12335343>) now! Thanks +Vinod > On Mar 30, 2016, at 4:18

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 about 2.7.3. Was previou

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 good time to remind/point folks to HA

Re: 2.7.3 release plan

; 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

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 aud

Re: 2.7.3 release plan

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. > > >>>>> > > >>>>> On Thu, Mar 31,

Re: 2.7.3 release plan

t;> wrote: > >>>>>> Thanks for bringing up this topic, Sean. > >>>>>> When I released our latest Hadoop release 2.6.4, the patch of > >>> HDFS-8791 > >>>>> haven't been committed in so that's why we didn't discuss thi

Re: 2.7.3 release plan

this layout change as a > > > >> Blocker bug that fixing a significant performance regression before > > but > > > not > > > >> a normal performance improvement. And I believe HDFS community already > > > did > > > >> their best with careful and patient to deliver the fix and other > > related

Re: 2.7.3 release plan

JIRA discussion, we treated this layout change as a >>>>> Blocker bug that fixing a significant performance regression before >> but >>> not >>>>> a normal performance improvement. And I believe HDFS community already >>> did >>>>> their best with careful and patient to deliver the f

Re: 2.7.3 release plan

as a >> > >> Blocker bug that fixing a significant performance regression before >> but >> > not >> > >> a normal performance improvement. And I believe HDFS community already >> > did >> > >> their best with careful and patient to deliver the fix and other >> related >> > &

Re: 2.7.3 release plan

a >> > >> Blocker bug that fixing a significant performance regression before >> but >> > not >> > >> a normal performance improvement. And I believe HDFS community already >> > did >> > >> their best with careful and patient to deliver the fix and other >> related >> > >

Re: 2.7.3 release plan

areful 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 committers, > > not to > > >> mention the outstanding performance test data in HDFS-8791. &

Re: 2.7.3 release plan

e 30+ rounds patch review back and forth by senior committers, > 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 > >> branch-2.7

Re: 2.7.3 release plan

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

> > > Junping > > > > ____ > > From: Sean Busbey > > Sent: Thursday, March 31, 2016 2:57 PM > > To: hdfs-dev@hadoop.apache.org > > Cc: Hadoop Common; yarn-...@hadoop.apache.org; > mapreduce-...@hadoop.apache.org &g

Re: 2.7.3 release plan

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 > > > From: Sean Busbey > Sent: Thursday, March 31, 2016 2:57 PM > To: hdfs-dev@hadoop.apache.o

Re: 2.7.3 release plan

x27;t see any blocker issue to bring it into 2.6.5 now. Just my 2 cents. Thanks, Junping From: Sean Busbey Sent: Thursday, March 31, 2016 2:57 PM To: hdfs-dev@hadoop.apache.org Cc: Hadoop Common; yarn-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org S

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 e

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 https://hadoop.apache.org/docs/stable/hadoop-project-d

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 / impr