Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
MIME-Version: 1.0
In-Reply-To: <15B9DA1D-FB0A-434C-8823-2404A3215AA7@hortonworks.com>
References: <A8D51C69-C7E4-43BE-B282-CEF3A8A6CFE5@hortonworks.com>
	<D1680255.20FCF%cnauroth@hortonworks.com>
	<8AD4EE147886274A8B495D6AF407DF698124E8DA@szxeml510-mbx.china.huawei.com>
	<5552E33F.8040502@oss.nttdata.co.jp>
	<CAO8sc+_w9JmDYwMRoas6w-r2ZLKbm4Oh_4YmnYe5ZAk4Zgki1Q@mail.gmail.com>
	<8AD4EE147886274A8B495D6AF407DF6981CDD5F9@szxeml510-mbx.china.huawei.com>
	<CAGHyZ6KvSn3P8Z33RE_YYvFTXgm2YTwB2yV25nTOoW+KW_agXw@mail.gmail.com>
	<33E1A54B-22AE-4214-9F26-97EFE33DBB3C@hortonworks.com>
	<6335EE2F-15A0-41F0-8FA2-D397E2DF54E5@hortonworks.com>
	<944F00D7-88B2-46FE-BD92-AC4FD06B2125@hortonworks.com>
	<55AE0DC5.4000001@oss.nttdata.co.jp>
	<CE1CD678-5ADA-459C-AB1C-7D9D9F7F7103@hortonworks.com>
	<CADbBEnvJ9Eykcr7CvjiEdrnL4aisJyTKY98GMUCri5xab7PPrA@mail.gmail.com>
	<40D02015-C0F6-4AE6-B871-E03EA8368EBF@hortonworks.com>
	<CADbBEntUYLjc_VXChhdNnVBxRXLfmRAO4vk-JeU5Gda-ZYW4YQ@mail.gmail.com>
	<CAD++eCksjCy8Q7+E0dYzYsN=MCWrU8JimJYK-0NiFjHESyUitg@mail.gmail.com>
	<D1E7A94A.22216%rhaase@pandora.com>
	<1438804608163.61990@hortonworks.com>
	<CAGHyZ6+7BH_OOPG8CEua1Dqs59wmQ+j=LcY_EghUq1x6nVMmZg@mail.gmail.com>
	<CADbBEnvdJrmkZphz1AWAtV9e7nTktNb4MWv_OKE44Uj+tPJJ7Q@mail.gmail.com>
	<CADoWKTCrwMbOuo3xH4ALEVHTwjZHhxw2LeetAZ6jYu6LXTe82g@mail.gmail.com>
	<F9CA745D-E708-4C8B-B567-2E33BAD4FDC7@hortonworks.com>
	<15B9DA1D-FB0A-434C-8823-2404A3215AA7@hortonworks.com>
Date: Wed, 9 Sep 2015 16:22:20 -0700
Message-ID: 
 <CAJP+fe4=ABF9rz5GsAqTJKN+i1ujSu=Um=k0WjNaojnq_KhN9A@mail.gmail.com>
Subject: Re: Planning Hadoop 2.6.1 release
From: Nikhil <mnikhil@gmail.com>
To: yarn-dev@hadoop.apache.org
Cc: Hadoop Common <common-dev@hadoop.apache.org>,
	"hdfs-dev@hadoop.apache.org" <hdfs-dev@hadoop.apache.org>,
	"mapreduce-dev@hadoop.apache.org" <mapreduce-dev@hadoop.apache.org>,
	"vinayakumarb@apache.org" <vinayakumarb@apache.org>
Content-Type: multipart/alternative; boundary=089e0122e6e81c192e051f58c13d

--089e0122e6e81c192e051f58c13d
Content-Type: text/plain; charset=UTF-8

Hi Vinod,

I am wondering if there is any news on 2.6.1 release. Any dates planned for
the release?

Nikhil


On Fri, Aug 14, 2015 at 12:23 PM, Vinod Kumar Vavilapalli <
vinodkv@hortonworks.com> wrote:

> To clarify, there is already a branch-2.6.1 created separately. So, if you
> want something in 2.6.2, you can continue putting it in branch-2.6.
>
> But no 2.6.1 related commits please.
>
> Thanks
> +Vinod
>
> > On Aug 14, 2015, at 12:09 PM, Vinod Kumar Vavilapalli <
> vinodkv@hortonworks.com> wrote:
> >
> > Everyone,
> >
> > Please stop committing to 2.6.1 (branch-2.6 or branch-2.6.1), we have a
> fairly elaborate parallel release-process going on for 2.6.1 (with me /
> Akira and Sangjin participating offline) and any outside cherry-picks are
> going to disrupt our progress.
> >
> > If you want something added to 2.6.1, please post it in the mailing
> lists and we will consider it.
> >
> > Thanks.
> > +Vinod
> >
> >> On Aug 14, 2015, at 12:17 AM, Vinayakumar B <vinayakumarb@apache.org>
> wrote:
> >>
> >> FYI, Some of the issues in
> >> https://wiki.apache.org/hadoop/Release-2.6.1-Working-Notes are already
> >> merged in 2.6.1.
> >>
> >>
> >>
> >> Regards,
> >> Vinay
> >>
> >> On Fri, Aug 14, 2015 at 12:43 PM, Sangjin Lee <sjlee@apache.org> wrote:
> >>
> >>> HDFS-8850 <https://issues.apache.org/jira/browse/HDFS-8850> is a fix
> for
> >>> VolumeScanner which was added to 2.7 (HDFS-7430
> >>> <https://issues.apache.org/jira/browse/HDFS-7430>). I don't see it
> >>> applicable to 2.6. Could you please confirm?
> >>>
> >>> Thanks,
> >>> Sangjin
> >>>
> >>> On Wed, Aug 5, 2015 at 2:34 PM, Sean Busbey <busbey@cloudera.com>
> wrote:
> >>>
> >>>> If we haven't frozen yet, HDFS-8850 is a straight forward fix that is
> >>>> currently only in 2.8+ and would benefit 2.6 and 2.7.
> >>>>
> >>>> On Wed, Aug 5, 2015 at 2:56 PM, Junping Du <jdu@hortonworks.com>
> wrote:
> >>>>
> >>>>> I would like to nominate YARN-3832 as 2.6.1 candidate which is
> critical
> >>>>> and I also saw it happened recently on a 2.6.0 cluster. Hope this is
> >>> not
> >>>>> too late.
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> Junping
> >>>>> ________________________________________
> >>>>> From: Rich Haase <rhaase@pandora.com>
> >>>>> Sent: Thursday, August 06, 2015 1:52 AM
> >>>>> To: mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
> >>>>> Cc: common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
> >>>>> Subject: Re: Planning Hadoop 2.6.1 release
> >>>>>
> >>>>> +1 to add those fixes.
> >>>>>
> >>>>>
> >>>>> Rich Haase | Sr. Software Engineer | Pandora
> >>>>> m 303.887.1146 | rhaase@pandora.com
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> On 8/5/15, 11:42 AM, "Wangda Tan" <wheeleast@gmail.com> wrote:
> >>>>>
> >>>>>> Can we add following two fixes to 2.6.1?
> >>>>>>
> >>>>>> https://issues.apache.org/jira/browse/YARN-2922 and
> >>>>>> https://issues.apache.org/jira/browse/YARN-3487.
> >>>>>>
> >>>>>> They're not fatal issue, but they can cause lots of issue in a large
> >>>>>> cluster.
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Wangda
> >>>>>>
> >>>>>>
> >>>>>> On Mon, Aug 3, 2015 at 1:21 PM, Sangjin Lee <sjlee@apache.org>
> wrote:
> >>>>>>
> >>>>>>> See my later update in the thread. HDFS-7704 is in the list.
> >>>>>>>
> >>>>>>> Thanks,
> >>>>>>> Sangjin
> >>>>>>>
> >>>>>>> On Mon, Aug 3, 2015 at 1:19 PM, Vinod Kumar Vavilapalli <
> >>>>>>> vinodkv@hortonworks.com> wrote:
> >>>>>>>
> >>>>>>>> Makes sense, it was caused by HDFS-7704 which got into 2.7.0 only
> >>>> and
> >>>>>>> is
> >>>>>>>> not part of the candidate list. Removed HDFS-7916 from the list.
> >>>>>>>>
> >>>>>>>> Thanks
> >>>>>>>> +Vinod
> >>>>>>>>
> >>>>>>>>> On Jul 24, 2015, at 6:32 PM, Sangjin Lee <sjlee@apache.org>
> >>>> wrote:
> >>>>>>>>>
> >>>>>>>>> Out of the JIRAs we proposed, please remove HDFS-7916. I don't
> >>>>>>> think it
> >>>>>>>>> applies to 2.6.
> >>>>>>>>>
> >>>>>>>>> Thanks,
> >>>>>>>>> Sangjin
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> Sean
> >>>>
> >>>
> >
>
>

--089e0122e6e81c192e051f58c13d--