Apologies for the disruption by commits to branch-2.6

I thought since the branch-2.6 already have the setup made for 2.6.1 its
ready for merging the commits from the list
https://wiki.apache.org/hadoop/Release-2.6.1-Working-Notes.

Cherry-picked only issues from the list and which were cleanly appliable.

-Vinay

On Sat, Aug 15, 2015 at 12:53 AM, Vinod Kumar Vavilapalli <
vino...@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 <
> vino...@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 <vinayakum...@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 <sj...@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 <bus...@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 <j...@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 <rha...@pandora.com>
> >>>>> Sent: Thursday, August 06, 2015 1:52 AM
> >>>>> To: mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
> >>>>> Cc: common-dev@hadoop.apache.org; hdfs-...@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 | rha...@pandora.com
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> On 8/5/15, 11:42 AM, "Wangda Tan" <wheele...@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 <sj...@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 <
> >>>>>>> vino...@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 <sj...@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
> >>>>
> >>>
> >
>
>

Reply via email to