Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
MIME-Version: 1.0
Sender: sjlee0@gmail.com
In-Reply-To: <CAD++eCkWKdr9yJKQdocfE11xQh2pnz+bd4e=bcQ4Go2PYJSHwQ@mail.gmail.com>
References: <CAMyYaRKomwk4L6ZupB1-V8d0EpYZzTDaHsQO4aWyXMPb8=y1Vg@mail.gmail.com>
 <A16F3F9A-2BE4-4FD1-A400-0A7892302C20@hortonworks.com> <CACO5Y4wQSkaZqz2CAypo1XVQWsXKxN8tJJeY=jhBqcOTQcF6+Q@mail.gmail.com>
 <CA+qbEUNR_Xg0E=Hc+kx+4NGqJeFh6d502bzf4+bBq=Z81ib7LQ@mail.gmail.com>
 <0C22896E-D77B-4DE4-99A2-9D81E150779C@hortonworks.com> <49120AE6-98D9-4CC2-A6A6-4C322A25F1D6@apache.org>
 <2A5F3F89-C79B-42BD-98AC-246CF33D4C47@apache.org> <BEF105DA-5239-41CC-A5D2-97BE6F6D48C8@apache.org>
 <33E01D1B-C416-464F-8E18-0B368A52DFF3@apache.org> <D2D7D715.BDBC%uma.gangumalla@intel.com>
 <CALwhT94QkLni-q8v2drFuz7aKUxMVzjxGM_mNBpLy=Lku105bg@mail.gmail.com>
 <D2D91AA7.3A575%cnauroth@hortonworks.com> <CAOScs9YnU8QHOkm8HH5MKn5mgCrNopW_0qpQr2twsGnZ2s2RzA@mail.gmail.com>
 <4B44247B-AFB2-4803-BDB0-251A8270F98C@apache.org> <2F9B8811-8240-454A-8599-64BE4B15CE2F@apache.org>
 <7CCEC640-5BCA-4ECC-976B-8630F4C0DD72@apache.org> <33841919-A63C-40BC-992D-9B98424BFBFC@hortonworks.com>
 <CADbBEnvug24nEd9iKmQfn33eZNXJ7uFbKGGgxWSRGZiynfqDPA@mail.gmail.com>
 <CAD++eCmT=eRHV0aASskQh0hqRPZYxTC6Ke_Kq-YbHXjNx+vhcA@mail.gmail.com>
 <CADbBEnuAykDQSRtLXp81StXK7sd76hpdDfa8V9S3Oh77RHZt+w@mail.gmail.com> <CAD++eCkWKdr9yJKQdocfE11xQh2pnz+bd4e=bcQ4Go2PYJSHwQ@mail.gmail.com>
From: Sangjin Lee <sjlee@apache.org>
Date: Wed, 11 May 2016 18:01:02 -0700
Message-ID: <CADbBEnuBZ6Ac+FcTJELSabpHUriSbGXP99o7QE7vUCjoX5ss2w@mail.gmail.com>
Subject: Re: [Release thread] 2.8.0 release activities
To: Wangda Tan <wheeleast@gmail.com>
Cc: "mapreduce-dev@hadoop.apache.org" <mapreduce-dev@hadoop.apache.org>,
	"yarn-dev@hadoop.apache.org" <yarn-dev@hadoop.apache.org>,
	"hdfs-dev@hadoop.apache.org" <hdfs-dev@hadoop.apache.org>,
	"common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>
Content-Type: multipart/alternative; boundary=001a113dcfc85f164e05329ab202
archived-at: Thu, 12 May 2016 01:01:31 -0000

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

I see the following list of JIRAs from HADOOP and HDFS as blockers for
2.8.0. Other JIRAs are either old issues with little movement or new issues
that don't appear to be as critical/ready.

- HADOOP-12893
- HADOOP-12892
- HADOOP-10940 (patch ready?)
- HADOOP-12971 (can be done relatively quickly?)
- HDFS-7959
- HDFS-7597 (needs review/some more work?)

I would propose moving the rest out of scope for 2.8.0 (23 JIRAs). Let me
know what you think.


On Wed, May 11, 2016 at 5:37 PM, Wangda Tan <wheeleast@gmail.com> wrote:

> Sounds good to me :).
>
> Jian and I have looked at all existing 2.8.0 blockers and criticals today=
.
> To me more than half of MR/YARN blockers/criticals of 2.8 should be moved
> out. Left comments on these JIRAs asked original owners, plan to update
> target version of these JIRAs early next week.
>
> Will keep this thread updated.
>
> Thanks,
> Wangda
>
>
> On Wed, May 11, 2016 at 5:06 PM, Sangjin Lee <sjlee@apache.org> wrote:
>
>> How about this? I'll review the HADOOP/HDFS bugs in that list to come up
>> with true blockers for 2.8.0 or JIRAs that are close to being ready. I'l=
l
>> report the list here. Then folks can chime in if you agree
>>
>> Perhaps Wangda, you can go over the YARN/MR bugs. Sound like a plan?
>>
>> Thanks,
>> Sangjin
>>
>> On Wed, May 11, 2016 at 4:26 PM, Wangda Tan <wheeleast@gmail.com> wrote:
>>
>>> +1, we should close such staled JIRAs to avoid doing unnecessary checks
>>> for
>>> every releases.
>>>
>>> I'm working on reviewing YARN/MR critical/blocker patches currently, it
>>> gonna very helpful if someone else can help with reviewing Common/HDFS
>>> JIRAs.
>>>
>>> Thanks,
>>> Wangda
>>>
>>>
>>> On Wed, May 11, 2016 at 4:20 PM, Sangjin Lee <sjlee@apache.org> wrote:
>>>
>>> > Where do we stand in terms of closing out blocker/critical issues for
>>> > 2.8.0? I still see 50 open JIRAs in Vinod's list:
>>> > https://issues.apache.org/jira/issues/?filter=3D12334985
>>> >
>>> > But I see a lot of JIRAs with no patches or very stale patches. It
>>> would be
>>> > a good exercise to come up with the list of JIRAs that we need to blo=
ck
>>> > 2.8.0 for and focus our attention on closing them out. Thoughts?
>>> >
>>> > Thanks,
>>> > Sangjin
>>> >
>>> > On Sat, Apr 23, 2016 at 5:05 AM, Steve Loughran <
>>> stevel@hortonworks.com>
>>> > wrote:
>>> >
>>> > >
>>> > > > On 23 Apr 2016, at 01:24, Vinod Kumar Vavilapalli <
>>> vinodkv@apache.org>
>>> > > wrote:
>>> > > >
>>> > > > We are not converging - there=E2=80=99s still 58 more. I need hel=
p from the
>>> > > community in addressing / review 2.8.0 blockers. If folks can start
>>> with
>>> > > reviewing Patch available tickets, that=E2=80=99ll be great.
>>> > > >
>>> > > >
>>> > >
>>> > >
>>> > > I'm still doing the s3a stuff, other people testing and reviewing
>>> this
>>> > > stuff welcome.
>>> > >
>>> > > in particular, I could do with others playing with this patch of
>>> mine,
>>> > > which adds counters and things into S3a, based on the azure
>>> > instrumentation
>>> > >
>>> > > https://issues.apache.org/jira/browse/HADOOP-13028
>>> > >
>>> > >
>>> > >
>>> >
>>>
>>
>>
>

--001a113dcfc85f164e05329ab202--