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/09/22 00:42:45 UTC
Release 0.5.1
Folks,
It looks like committers are pulling in most of their commits to branch-0.5
from master. There are only a few items like new tests etc. that are in
master but not in branch-0.5.
Given the above, it may make sense to snap the current master branch to
branch-0.5 and take all changes for the 0.5.1 release. If anyone has
committed changes to master that they don’t want to have in 0.5.1 then
please respond to this thread.
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: Release 0.5.1
Posted by Bikas Saha <bi...@hortonworks.com>.
Not heard any concerns on this thread. I will snap current master to
branch-0.5 to create the 0.5.1 release.
Bikas
-----Original Message-----
From: Rajesh Balamohan [mailto:rbalamohan@apache.org]
Sent: Wednesday, September 24, 2014 5:22 PM
To: dev@tez.apache.org
Subject: Re: Release 0.5.1
>>
It may make sense to snap the current master branch tobranch-0.5 and take
all changes for the 0.5.1 release.
>>
+1
IMO TEZ-1157 (Optimize broadcast shuffle) is a major change which exists in
master and not in branch-0.5. It would be great to pull in TEZ-1157 into
branch-0.5.
~Rajesh.B
On Mon, Sep 22, 2014 at 4:12 AM, Bikas Saha <bi...@hortonworks.com> wrote:
> Folks,
>
>
>
> It looks like committers are pulling in most of their commits to
> branch-0.5 from master. There are only a few items like new tests etc.
> that are in master but not in branch-0.5.
>
>
>
> Given the above, it may make sense to snap the current master branch
> to
> branch-0.5 and take all changes for the 0.5.1 release. If anyone has
> committed changes to master that they don’t want to have in 0.5.1 then
> please respond to this thread.
>
>
>
> 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.
>
--
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: Release 0.5.1
Posted by Rajesh Balamohan <rb...@apache.org>.
>>
It may make sense to snap the current master branch tobranch-0.5 and take
all changes for the 0.5.1 release.
>>
+1
IMO TEZ-1157 (Optimize broadcast shuffle) is a major change which exists in
master and not in branch-0.5. It would be great to pull in TEZ-1157 into
branch-0.5.
~Rajesh.B
On Mon, Sep 22, 2014 at 4:12 AM, Bikas Saha <bi...@hortonworks.com> wrote:
> Folks,
>
>
>
> It looks like committers are pulling in most of their commits to branch-0.5
> from master. There are only a few items like new tests etc. that are in
> master but not in branch-0.5.
>
>
>
> Given the above, it may make sense to snap the current master branch to
> branch-0.5 and take all changes for the 0.5.1 release. If anyone has
> committed changes to master that they don’t want to have in 0.5.1 then
> please respond to this thread.
>
>
>
> 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.
>