Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
MIME-Version: 1.0
Sender: sjlee0@gmail.com
In-Reply-To: 
 <CADbBEnsowU8yKmnLaDbO1N8U51xo=EZ2TmG41WYjVLKfXzV5Gw@mail.gmail.com>
References: 
 <CAMyYaRLbfzjeTQrw+T2_kn3PmfzaC5MevN467=L9XD+n+SbiLQ@mail.gmail.com>
 <CADbBEnuGDe2EdSo7FyV3fXqPakfaFB7BJim8QxRYZ9uqkdgrtQ@mail.gmail.com>
 <F55AB186-55D2-437A-9CD3-DD7C911267A2@hortonworks.com>
 <CADoWKTBNCgdjdVt_rN0q=be872c5t4SYWHKUYanbYZdY0g8usw@mail.gmail.com>
 <5604CFFE.9000609@oss.nttdata.co.jp>
 <CADbBEnsZsQVQDWvH141+Co4h19=XLPWs8Ufnq8pTZcGtcHEBZg@mail.gmail.com>
 <CADbBEnsowU8yKmnLaDbO1N8U51xo=EZ2TmG41WYjVLKfXzV5Gw@mail.gmail.com>
From: Sangjin Lee <sjlee@apache.org>
Date: Sat, 26 Sep 2015 09:19:49 -0700
Message-ID: 
 <CADbBEnsmu2q7RzYqHmS7tw_e=mfcXBHOOKDr2o+nhkLf5+r4aw@mail.gmail.com>
Subject: Re: Planning for Apache Hadoop 2.6.2
To: "mapreduce-dev@hadoop.apache.org" <mapreduce-dev@hadoop.apache.org>
Cc: "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>,
	"hdfs-dev@hadoop.apache.org" <hdfs-dev@hadoop.apache.org>,
	"yarn-dev@hadoop.apache.org" <yarn-dev@hadoop.apache.org>
Content-Type: multipart/alternative; boundary=047d7b33c67c82290c0520a8d64e

--047d7b33c67c82290c0520a8d64e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I have updated branch-2.6 and force pushed the branch. I checked the branch
out from scratch and tested building it.

Branch-2.6 is back open. If you have a patch ready for 2.6.2, double check
if it applies cleanly before committing to branch-2.6.

Thanks,
Sangjin

On Fri, Sep 25, 2015 at 4:42 PM, Sangjin Lee <sjlee@apache.org> wrote:

> Per Vinod's suggestion, in order to reduce the amount of movement I'll
> pick commits from branch-2.6 onto the tip of branch-2.6.1 rather than the
> other way around. This means I'll need to move branch-2.6 and force push
> that change.
>
> Could you please hold off on committing to branch-2.6 until I am done
> relocating the branch? I'll let you know when I'm done with that exercise=
.
> I expect I'll be done with this in 24 hours or so. Let me know if you hav=
e
> any concerns.
>
> Thanks,
> Sangjin
>
> On Fri, Sep 25, 2015 at 12:53 PM, Sangjin Lee <sjlee@apache.org> wrote:
>
>> Thanks folks. I'll get started on the items Vinod mentioned soon.
>>
>> If you have something you'd like to push for inclusion in 2.6.2, please
>> mark the target version as 2.6.2.
>>
>> I'd like to ask one more thing on top of that. It would be AWESOME if yo=
u
>> can check if it can be applied cleanly on top of 2.6.1, and if not, prov=
ide
>> an updated patch suitable for 2.6.1. This will help speed up the 2.6.2
>> release process tremendously. If the person who's recommending the JIRA =
for
>> 2.6.2 inclusion can do it, that would be great. Help from the original
>> contributor might be helpful as well. Thanks for your cooperation!
>>
>> Regards,
>> Sangjin
>>
>> On Thu, Sep 24, 2015 at 9:39 PM, Akira AJISAKA <
>> ajisakaa@oss.nttdata.co.jp> wrote:
>>
>>> Thanks Vinod and Sangjin for releasing 2.6.1 and starting discussion fo=
r
>>> 2.6.2!
>>>
>>> +1. If there's anything I can help you with, please tell me.
>>>
>>> Thanks,
>>> Akira
>>>
>>>
>>> On 9/25/15 13:23, Vinayakumar B wrote:
>>>
>>>> Thanks Vinod and Sangjin for making 2.6.1 release possible.
>>>>
>>>> Apologies for not getting time to verify and vote for the release.
>>>>
>>>> I will also be available to help for 2.6.2 if anything required.
>>>>
>>>> Thanks,
>>>> Vinay
>>>>
>>>> On Fri, Sep 25, 2015 at 12:16 AM, Vinod Vavilapalli <
>>>> vinodkv@hortonworks.com
>>>>
>>>>> wrote:
>>>>>
>>>>
>>>> +1. Please take it over, I=E2=80=99ll standby for any help needed.
>>>>>
>>>>> Thanks
>>>>> +Vinod
>>>>>
>>>>>
>>>>> On Sep 24, 2015, at 11:34 AM, Sangjin Lee <sjlee@apache.org<mailto:
>>>>> sjlee@apache.org>> wrote:
>>>>>
>>>>> I'd like to volunteer as the release manager for 2.6.2 unless there i=
s
>>>>> an
>>>>> objection.
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>

--047d7b33c67c82290c0520a8d64e--