Re: 2.7.3 release plan

2016-07-22 Thread Vinod Kumar Vavilapalli
The nexus issue persists to date. I have been constantly getting “Remote end closed due to a SSH handshake” issue. Tried to upload the artifacts in piece, but that was too slow, spanned across days. Finally found a “ DretryFailedDeploymentCount=10” option to mvn-deploy. Sending out the vote

Re: 2.7.3 release plan

2016-07-13 Thread Vinod Kumar Vavilapalli
HADOOP-12893 is done after 4 months, thanks to great work from a bunch of folks besides Xiao Chen. Creating the RC now. Thanks +Vinod > On Jun 14, 2016, at 7:28 PM, Vinod Kumar Vavilapalli > wrote: > > Release branch 2.7.3 is created. I also updated branch-2.7 to point

Re: 2.7.3 release plan

2016-06-14 Thread Vinod Kumar Vavilapalli
Release branch 2.7.3 is created. I also updated branch-2.7 to point to 2.7.4-SNAPSHOT now. Thanks +Vinod > On Jun 14, 2016, at 3:54 PM, Vinod Kumar Vavilapalli > wrote: > > HADOOP-12893 is finally close to completion after > 3months thanks to > efforts from Akira

Re: 2.7.3 release plan

2016-06-14 Thread Vinod Kumar Vavilapalli
HADOOP-12893 is finally close to completion after > 3months thanks to efforts from Akira AJISAKA, Xiao Chen and Andrew Wang. I’m creating the release branch and kickstarting the release activities. Thanks +Vinod > On May 16, 2016, at 5:39 PM, Vinod Kumar Vavilapalli >

Re: 2.7.3 release plan

2016-05-16 Thread Vinod Kumar Vavilapalli
I am just waiting on HADOOP-12893. HADOOP-13154 just got created in the last one day, will have to see if it really should block the release. Major tickets are usually taken on a time basis: if they get in by the proposed timelines, we get them in. Otherwise, we move them over. Thanks +Vinod

Re: 2.7.3 release plan

2016-05-16 Thread larry mccay
Curious on the status of 2.7.3 It seems that we still have two outstanding critical/blocker JIRAs: 1. [image: Bug] HADOOP-12893 Verify LICENSE.txt and NOTICE.txt 2. [image: Sub-task] HADOOP-13154

Re: 2.7.3 release plan

2016-04-12 Thread Vinod Kumar Vavilapalli
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

2016-04-11 Thread Colin McCabe
gt; > policy. That includes > > > > * Source release artifact > > * any convenience binary artifacts places on dist.apache > > * any convenience jars put into the ASF Nexus repository > > > > That likely means that we bundle much more than just what's in the source > > tree. > > > > (Though this sounds like we're getting off topic for the 2.7.3 release > > plan.) > > > > -- > > busbey >

Re: 2.7.3 release plan

2016-04-07 Thread Vinod Kumar Vavilapalli
nary artifacts places on dist.apache > * any convenience jars put into the ASF Nexus repository > > That likely means that we bundle much more than just what's in the source > tree. > > (Though this sounds like we're getting off topic for the 2.7.3 release plan.) > > -- > busbey

Re: 2.7.3 release plan

2016-04-07 Thread Sean Busbey
ASF Nexus repository That likely means that we bundle much more than just what's in the source tree. (Though this sounds like we're getting off topic for the 2.7.3 release plan.) -- busbey

Re: 2.7.3 release plan

2016-04-06 Thread Colin McCabe
In general, the only bundled native component I can see is lz4. I guess debatably we should add tree.h to the NOTICE file as well, since it came from BSD and is licensed under that license. Please keep in mind bundling means "included in the source tree", NOT "downloaded during the build

Re: 2.7.3 release plan

2016-04-06 Thread Kihwal Lee
rg>; hdfs-...@hadoop.apache.org; mapreduce-...@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

2016-04-06 Thread Vinod Kumar Vavilapalli
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

2016-04-06 Thread Vinod Kumar Vavilapalli
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

2016-04-06 Thread Vinod Kumar Vavilapalli
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

2016-04-06 Thread Allen Wittenauer
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

2016-04-05 Thread Andrew Wang
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

2016-04-05 Thread Chris Trezzo
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

2016-04-04 Thread Vinod Kumar Vavilapalli
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

2016-04-03 Thread Haohui Mai
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

2016-04-01 Thread Chris Trezzo
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

2016-04-01 Thread Andrew Purtell
nfirmation 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

2016-04-01 Thread Andrew Wang
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

2016-04-01 Thread Akira AJISAKA
, 2016 12:15 PM To: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; yarn-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org Subject: 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 dow

Re: 2.7.3 release plan

2016-04-01 Thread payam rastogi
he.org Subject: 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.apac

Re: 2.7.3 release plan

2016-03-31 Thread Andrew Wang
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-...@hado

Re: 2.7.3 release plan

2016-03-31 Thread Sean Busbey
dfs-...@hadoop.apache.org > Cc: Hadoop Common; yarn-...@hadoop.apache.org; mapreduce-...@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

2016-03-31 Thread Junping Du
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

2016-03-31 Thread Sean Busbey
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

2016-03-31 Thread Akira AJISAKA
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