Yes. The relevant jiras have just been marked as blockers.

-----Original Message-----
From: Chris K Wensel [mailto:[email protected]]
Sent: Friday, July 25, 2014 2:08 PM
To: [email protected]
Cc: [email protected]
Subject: Re: 0.5 blockers


why not, TEZ-684.

https://issues.apache.org/jira/browse/TEZ-684

On Jul 24, 2014, at 7:21 PM, Bikas Saha <[email protected]> wrote:

> Folks,
>
>
>
> Here are the blockers for 0.5.
>
> https://issues.apache.org/jira/browse/TEZ-1311?jql=project%20%3D%20TEZ
> %20AND%20resolution%20%3D%20Unresolved%20AND%20priority%20%3D%20Blocke
> r%20ORDER%20BY%20key%20DESC
>
>
>
> Please add to the list in case something is missing. Only API
> stability issues should make it to the blocker list since 0.5 is
> expected to be an API stable release. Addition of a API's is possible
> after 0.5. So new API's don't need to be included in this list.
>
>
>
> Thanks
>
> Bikas
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or
> entity to which it is addressed and may contain information that is
> confidential, privileged and exempt from disclosure under applicable
> law. If the reader of this message is not the intended recipient, you
> are hereby notified that any printing, copying, dissemination,
> distribution, disclosure or forwarding of this communication is
> strictly prohibited. If you have received this communication in error,
> please contact the sender immediately and delete it from your system.
Thank You.

--
Chris K Wensel
[email protected]
http://concurrentinc.com

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Reply via email to