You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tez.apache.org by Bikas Saha <bi...@hortonworks.com> on 2014/08/26 22:24:15 UTC
Update for 0.5.0 RC3
Folks,
Looks like we need a breaking change for RC3 due to
https://issues.apache.org/jira/browse/TEZ-1500.
At this point, by looking at CHANGES.txt and git log, other than TEZ-1360,
the rest of the changes look like useful bug fixes. TEZ-1360 seems like a
useful and simple API addition that should not break anything.
At this point, I am considering getting rid of the existing 0.5 branches
and branching off fresh from master, thereby including all the bug-fixes.
If anyone has questions/comments/concerns then please respond to this
email. I will be committing the relevant blocking jiras to master and
creating a new RC tomorrow according to the above plan (barring new
regressions).
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.
Re: Update for 0.5.0 RC3
Posted by Siddharth Seth <ss...@apache.org>.
+1 for pulling everything in, and re-creating the branches.
On Tue, Aug 26, 2014 at 1:24 PM, Bikas Saha <bi...@hortonworks.com> wrote:
> Folks,
>
>
>
> Looks like we need a breaking change for RC3 due to
> https://issues.apache.org/jira/browse/TEZ-1500.
>
>
>
> At this point, by looking at CHANGES.txt and git log, other than TEZ-1360,
> the rest of the changes look like useful bug fixes. TEZ-1360 seems like a
> useful and simple API addition that should not break anything.
>
>
>
> At this point, I am considering getting rid of the existing 0.5 branches
> and branching off fresh from master, thereby including all the bug-fixes.
> If anyone has questions/comments/concerns then please respond to this
> email. I will be committing the relevant blocking jiras to master and
> creating a new RC tomorrow according to the above plan (barring new
> regressions).
>
>
>
> 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.
Re: Update for 0.5.0 RC3
Posted by Siddharth Seth <ss...@apache.org>.
+1 for pulling everything in, and re-creating the branches.
On Tue, Aug 26, 2014 at 1:24 PM, Bikas Saha <bi...@hortonworks.com> wrote:
> Folks,
>
>
>
> Looks like we need a breaking change for RC3 due to
> https://issues.apache.org/jira/browse/TEZ-1500.
>
>
>
> At this point, by looking at CHANGES.txt and git log, other than TEZ-1360,
> the rest of the changes look like useful bug fixes. TEZ-1360 seems like a
> useful and simple API addition that should not break anything.
>
>
>
> At this point, I am considering getting rid of the existing 0.5 branches
> and branching off fresh from master, thereby including all the bug-fixes.
> If anyone has questions/comments/concerns then please respond to this
> email. I will be committing the relevant blocking jiras to master and
> creating a new RC tomorrow according to the above plan (barring new
> regressions).
>
>
>
> 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.