Return-Path: X-Original-To: apmail-hadoop-common-dev-archive@www.apache.org Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B502A17D00 for ; Mon, 30 Mar 2015 21:05:11 +0000 (UTC) Received: (qmail 81655 invoked by uid 500); 30 Mar 2015 21:05:08 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 81570 invoked by uid 500); 30 Mar 2015 21:05:08 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-dev@hadoop.apache.org Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 81524 invoked by uid 99); 30 Mar 2015 21:05:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Mar 2015 21:05:08 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ricetons@gmail.com designates 209.85.214.178 as permitted sender) Received: from [209.85.214.178] (HELO mail-ob0-f178.google.com) (209.85.214.178) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Mar 2015 21:05:03 +0000 Received: by obbec2 with SMTP id ec2so2549315obb.3; Mon, 30 Mar 2015 14:04:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=RuRAHj5747TXQgctSicHRAu6bsyA2lutiqezUU9CeoQ=; b=VCZFG78crejj3xr+AULufMtfN9eCGG0/zX1nmPj77oXZ1N+8TASxHv6nNLS9SJZO1d mPaSP83bbMKuQcvFsC+R4HiMBbo7KFdg3W6wW6ozsyyj3xBtldMbT3lhwGOvSaBN1oS8 MXRfkf8dH50K4p1EN+d0zGDbzg/xDQdhOw0ZYGm/GxWBmj+nibeLUxM1uOJouBSo9MoG 5uAUWlhNn1V74j2ZWXEhJ4Ggr6WXkNaMPg5lswuYvBDXGdN4jcC2uhPxDvGETpDvf1Fb qV+8kDj7foFCqiAyHlQIGWVy5PMg5EmVlfn8IALWG4TrKGAwQeXpZqIJIEX9Tulk/Ci/ bv9g== MIME-Version: 1.0 X-Received: by 10.60.134.237 with SMTP id pn13mr29362964oeb.59.1427749483172; Mon, 30 Mar 2015 14:04:43 -0700 (PDT) Received: by 10.60.145.100 with HTTP; Mon, 30 Mar 2015 14:04:43 -0700 (PDT) In-Reply-To: References: <2059746485.2654630.1423843863610.JavaMail.yahoo@mail.yahoo.com> <1425239010159.37330@hortonworks.com> <1425239892312.98627@hortonworks.com> <9CE562F2-4F15-4BC7-887E-B2B50EF0050A@hortonworks.com> <9D8E213F-6DEB-4670-B7FB-EEC589410AA9@hortonworks.com> Date: Mon, 30 Mar 2015 14:04:43 -0700 Message-ID: Subject: Re: 2.7 status From: Mai Haohui To: hdfs-dev@hadoop.apache.org Cc: "mapreduce-dev@hadoop.apache.org" , "yarn-dev@hadoop.apache.org" , Hadoop Common Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org Just swept all the 2.7 blockers from the HDFS side. From the HDFS prospective 2.7 should be good to go. ~Haohui On Wed, Mar 25, 2015 at 11:47 AM, Konstantin Shvachko wrote: > Progress is good! > What are the four blockers? > Could you please mark them as such in the Jira. > > Thanks, > --Konst > > On Wed, Mar 25, 2015 at 9:53 AM, Vinod Kumar Vavilapalli < > vinodkv@hortonworks.com> wrote: > >> Progress has been really slow, but now we are down to four blockers across >> the board. >> >> I plan to roll an RC this weekend. >> >> Thanks, >> +Vinod >> >> On Mar 8, 2015, at 8:40 PM, Vinod Kumar Vavilapalli < >> vinodkv@hortonworks.com> wrote: >> >> > 2.7 branch created and branch-2 updated to point to 2.8-SNAPSHOT. >> > >> > Committers, please exercise caution on the content going into >> branch-2.7. I'd take help everyone's help in pushing through the remaining >> set of blockers targeted for 2.7. >> > >> > Thanks, >> > +Vinod >> > >> > On Mar 8, 2015, at 8:21 PM, Vinod Kumar Vavilapalli < >> vinodkv@hortonworks.com> wrote: >> > >> >> Branching 2.7 now. Request holding off commits to branch-2 to avoid >> commit race. Will send an all-clear in the next 30 mins once I am done. >> >> >> >> Thanks >> >> +Vinod >> >> >> >> On Mar 5, 2015, at 1:56 PM, Vinod Kumar Vavilapalli < >> vinodkv@hortonworks.com> wrote: >> >> >> >>> >> >>> The 2.7 blocker JIRA went down and going back up again, we will need >> to converge. >> >>> >> >>> Unless I see objections, I plan to cut a branch this weekend and >> selectively filter stuff in after that in the interest of convergence. >> >>> >> >>> Thoughts welcome! >> >>> >> >>> Thanks, >> >>> +Vinod >> >>> >> >>> On Mar 1, 2015, at 11:58 AM, Arun Murthy wrote: >> >>> >> >>>> Sounds good, thanks for the help Vinod! >> >>>> >> >>>> Arun >> >>>> >> >>>> ________________________________________ >> >>>> From: Vinod Kumar Vavilapalli >> >>>> Sent: Sunday, March 01, 2015 11:43 AM >> >>>> To: Hadoop Common; Jason Lowe; Arun Murthy >> >>>> Subject: Re: 2.7 status >> >>>> >> >>>> Agreed. How about we roll an RC end of this week? As a Java 7+ >> release with features, patches that already got in? >> >>>> >> >>>> Here's a filter tracking blocker tickets - >> https://issues.apache.org/jira/issues/?filter=12330598. Nine open now. >> >>>> >> >>>> +Arun >> >>>> Arun, I'd like to help get 2.7 out without further delay. Do you mind >> me taking over release duties? >> >>>> >> >>>> Thanks, >> >>>> +Vinod >> >>>> ________________________________________ >> >>>> From: Jason Lowe >> >>>> Sent: Friday, February 13, 2015 8:11 AM >> >>>> To: common-dev@hadoop.apache.org >> >>>> Subject: Re: 2.7 status >> >>>> >> >>>> I'd like to see a 2.7 release sooner than later. It has been almost >> 3 months since Hadoop 2.6 was released, and there have already been 634 >> JIRAs committed to 2.7. That's a lot of changes waiting for an official >> release. >> >>>> >> https://issues.apache.org/jira/issues/?jql=project%20in%20%28hadoop%2Chdfs%2Cyarn%2Cmapreduce%29%20AND%20fixversion%3D2.7.0%20AND%20resolution%3DFixed >> >>>> Jason >> >>>> >> >>>> From: Sangjin Lee >> >>>> To: "common-dev@hadoop.apache.org" >> >>>> Sent: Tuesday, February 10, 2015 1:30 PM >> >>>> Subject: 2.7 status >> >>>> >> >>>> Folks, >> >>>> >> >>>> What is the current status of the 2.7 release? I know initially it >> started >> >>>> out as a "java-7" only release, but looking at the JIRAs that is very >> much >> >>>> not the case. >> >>>> >> >>>> Do we have a certain timeframe for 2.7 or is it time to discuss it? >> >>>> >> >>>> Thanks, >> >>>> Sangjin >> >>>> >> >>> >> >> >> > >> >>