You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tez.apache.org by Hitesh Shah <hi...@apache.org> on 2014/02/14 23:53:56 UTC
[DISCUSS] Targeting a 0.3.0-incubating release
Hello folks,
Given that our last release was in early December, 2013, it seems like a good time to target a new release. I believe most of the critical security related fixes have gone in and the few that remain in TEZ-669 could be targeted for a future release.
I have marked a few jiras that could be considered blockers for a 0.3.0 release to ensure good usability ( the list is open for discussion - feel free to add any other issues if you deem them to be blockers ):
https://issues.apache.org/jira/issues/?jql=project%20%3D%20TEZ%20AND%20resolution%20%3D%20Unresolved%20AND%20priority%20%3D%20Blocker%20ORDER%20BY%20key%20DESC
Once, these fixes go in, I can aim to make a release sometime next week.
Comments/concerns/suggestions?
thanks
-- Hitesh
Re: [DISCUSS] Targeting a 0.3.0-incubating release
Posted by Tsuyoshi OZAWA <oz...@gmail.com>.
Thank you for clarifying, Hitesh.
I've been excited that Hive and Pig folks will catch up with Tez changes.
Thanks,
- Tsuyoshi
On Tue, Feb 18, 2014 at 11:17 AM, Hitesh Shah <hi...@apache.org> wrote:
> Hi Tsuyoshi,
>
> Short answer to your question is yes, the pig/hive folks should move to 0.3.0 sooner rather than later ( but there is no reason they cannot stick to 0.2.0 ). From the tez community point of view, given that we are still in the early stages of the product, we would like to see a fast moving project and push the onus on users to upgrade to newer versions to get both new features, perf improvements as well as bug fixes. This policy will change however as both Hive and Pig moves towards production-ready releases though.
>
> Having talked to both the Hive and Pig folks offline, here is what I know:
>
> - Hive has been using the 0.2.0 release and will likely move to 0.3.0 given that some of the new features such as Vertex Groups, custom edges are being used by Hive in their tez branch.
> - Pig currently uses the latest snapshots from the master branch and depending on their release timelines, will move to either using the 0.3.0 release or 0.4.0 if it is available by then. Bikas is looking at addressing a lot of the API cleanup for 0.4.0 though which the Pig folks will have to handle if they move to 0.4.0.
>
> I have CC'ed some of the Hive and Pig folks if they would like to chime in.
>
> thanks
> -- Hitesh
>
> On Feb 18, 2014, at 10:49 AM, Tsuyoshi OZAWA wrote:
>
>> Hi,
>>
>> About 0.3 release itself, LGTM :-) Let's go ahead.
>>
>> One my question is how to collaborate with application
>> developers like Hive or Pig project.
>> Should these developers be recommended to upgrade
>> from 0.2 to 0.3?
>> We should clarify the polity against the application developers
>> though I know Tez is in alpha stage. What do you think?
>>
>> Thanks, Tsuyoshi
>>
>>
>> On Fri, Feb 14, 2014 at 2:53 PM, Hitesh Shah <hi...@apache.org> wrote:
>>> Hello folks,
>>>
>>> Given that our last release was in early December, 2013, it seems like a good time to target a new release. I believe most of the critical security related fixes have gone in and the few that remain in TEZ-669 could be targeted for a future release.
>>>
>>> I have marked a few jiras that could be considered blockers for a 0.3.0 release to ensure good usability ( the list is open for discussion - feel free to add any other issues if you deem them to be blockers ):
>>>
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20TEZ%20AND%20resolution%20%3D%20Unresolved%20AND%20priority%20%3D%20Blocker%20ORDER%20BY%20key%20DESC
>>>
>>> Once, these fixes go in, I can aim to make a release sometime next week.
>>>
>>> Comments/concerns/suggestions?
>>>
>>> thanks
>>> -- Hitesh
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>> --
>> - Tsuyoshi
>
--
- Tsuyoshi
Re: [DISCUSS] Targeting a 0.3.0-incubating release
Posted by Tsuyoshi OZAWA <oz...@gmail.com>.
Thank you for clarifying, Hitesh.
I've been excited that Hive and Pig folks will catch up with Tez changes.
Thanks,
- Tsuyoshi
On Tue, Feb 18, 2014 at 11:17 AM, Hitesh Shah <hi...@apache.org> wrote:
> Hi Tsuyoshi,
>
> Short answer to your question is yes, the pig/hive folks should move to 0.3.0 sooner rather than later ( but there is no reason they cannot stick to 0.2.0 ). From the tez community point of view, given that we are still in the early stages of the product, we would like to see a fast moving project and push the onus on users to upgrade to newer versions to get both new features, perf improvements as well as bug fixes. This policy will change however as both Hive and Pig moves towards production-ready releases though.
>
> Having talked to both the Hive and Pig folks offline, here is what I know:
>
> - Hive has been using the 0.2.0 release and will likely move to 0.3.0 given that some of the new features such as Vertex Groups, custom edges are being used by Hive in their tez branch.
> - Pig currently uses the latest snapshots from the master branch and depending on their release timelines, will move to either using the 0.3.0 release or 0.4.0 if it is available by then. Bikas is looking at addressing a lot of the API cleanup for 0.4.0 though which the Pig folks will have to handle if they move to 0.4.0.
>
> I have CC'ed some of the Hive and Pig folks if they would like to chime in.
>
> thanks
> -- Hitesh
>
> On Feb 18, 2014, at 10:49 AM, Tsuyoshi OZAWA wrote:
>
>> Hi,
>>
>> About 0.3 release itself, LGTM :-) Let's go ahead.
>>
>> One my question is how to collaborate with application
>> developers like Hive or Pig project.
>> Should these developers be recommended to upgrade
>> from 0.2 to 0.3?
>> We should clarify the polity against the application developers
>> though I know Tez is in alpha stage. What do you think?
>>
>> Thanks, Tsuyoshi
>>
>>
>> On Fri, Feb 14, 2014 at 2:53 PM, Hitesh Shah <hi...@apache.org> wrote:
>>> Hello folks,
>>>
>>> Given that our last release was in early December, 2013, it seems like a good time to target a new release. I believe most of the critical security related fixes have gone in and the few that remain in TEZ-669 could be targeted for a future release.
>>>
>>> I have marked a few jiras that could be considered blockers for a 0.3.0 release to ensure good usability ( the list is open for discussion - feel free to add any other issues if you deem them to be blockers ):
>>>
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20TEZ%20AND%20resolution%20%3D%20Unresolved%20AND%20priority%20%3D%20Blocker%20ORDER%20BY%20key%20DESC
>>>
>>> Once, these fixes go in, I can aim to make a release sometime next week.
>>>
>>> Comments/concerns/suggestions?
>>>
>>> thanks
>>> -- Hitesh
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>> --
>> - Tsuyoshi
>
--
- Tsuyoshi
Re: [DISCUSS] Targeting a 0.3.0-incubating release
Posted by Hitesh Shah <hi...@apache.org>.
Hi Tsuyoshi,
Short answer to your question is yes, the pig/hive folks should move to 0.3.0 sooner rather than later ( but there is no reason they cannot stick to 0.2.0 ). From the tez community point of view, given that we are still in the early stages of the product, we would like to see a fast moving project and push the onus on users to upgrade to newer versions to get both new features, perf improvements as well as bug fixes. This policy will change however as both Hive and Pig moves towards production-ready releases though.
Having talked to both the Hive and Pig folks offline, here is what I know:
- Hive has been using the 0.2.0 release and will likely move to 0.3.0 given that some of the new features such as Vertex Groups, custom edges are being used by Hive in their tez branch.
- Pig currently uses the latest snapshots from the master branch and depending on their release timelines, will move to either using the 0.3.0 release or 0.4.0 if it is available by then. Bikas is looking at addressing a lot of the API cleanup for 0.4.0 though which the Pig folks will have to handle if they move to 0.4.0.
I have CC'ed some of the Hive and Pig folks if they would like to chime in.
thanks
-- Hitesh
On Feb 18, 2014, at 10:49 AM, Tsuyoshi OZAWA wrote:
> Hi,
>
> About 0.3 release itself, LGTM :-) Let's go ahead.
>
> One my question is how to collaborate with application
> developers like Hive or Pig project.
> Should these developers be recommended to upgrade
> from 0.2 to 0.3?
> We should clarify the polity against the application developers
> though I know Tez is in alpha stage. What do you think?
>
> Thanks, Tsuyoshi
>
>
> On Fri, Feb 14, 2014 at 2:53 PM, Hitesh Shah <hi...@apache.org> wrote:
>> Hello folks,
>>
>> Given that our last release was in early December, 2013, it seems like a good time to target a new release. I believe most of the critical security related fixes have gone in and the few that remain in TEZ-669 could be targeted for a future release.
>>
>> I have marked a few jiras that could be considered blockers for a 0.3.0 release to ensure good usability ( the list is open for discussion - feel free to add any other issues if you deem them to be blockers ):
>>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20TEZ%20AND%20resolution%20%3D%20Unresolved%20AND%20priority%20%3D%20Blocker%20ORDER%20BY%20key%20DESC
>>
>> Once, these fixes go in, I can aim to make a release sometime next week.
>>
>> Comments/concerns/suggestions?
>>
>> thanks
>> -- Hitesh
>>
>>
>>
>>
>>
>
>
>
> --
> - Tsuyoshi
Re: [DISCUSS] Targeting a 0.3.0-incubating release
Posted by Hitesh Shah <hi...@apache.org>.
Hi Tsuyoshi,
Short answer to your question is yes, the pig/hive folks should move to 0.3.0 sooner rather than later ( but there is no reason they cannot stick to 0.2.0 ). From the tez community point of view, given that we are still in the early stages of the product, we would like to see a fast moving project and push the onus on users to upgrade to newer versions to get both new features, perf improvements as well as bug fixes. This policy will change however as both Hive and Pig moves towards production-ready releases though.
Having talked to both the Hive and Pig folks offline, here is what I know:
- Hive has been using the 0.2.0 release and will likely move to 0.3.0 given that some of the new features such as Vertex Groups, custom edges are being used by Hive in their tez branch.
- Pig currently uses the latest snapshots from the master branch and depending on their release timelines, will move to either using the 0.3.0 release or 0.4.0 if it is available by then. Bikas is looking at addressing a lot of the API cleanup for 0.4.0 though which the Pig folks will have to handle if they move to 0.4.0.
I have CC'ed some of the Hive and Pig folks if they would like to chime in.
thanks
-- Hitesh
On Feb 18, 2014, at 10:49 AM, Tsuyoshi OZAWA wrote:
> Hi,
>
> About 0.3 release itself, LGTM :-) Let's go ahead.
>
> One my question is how to collaborate with application
> developers like Hive or Pig project.
> Should these developers be recommended to upgrade
> from 0.2 to 0.3?
> We should clarify the polity against the application developers
> though I know Tez is in alpha stage. What do you think?
>
> Thanks, Tsuyoshi
>
>
> On Fri, Feb 14, 2014 at 2:53 PM, Hitesh Shah <hi...@apache.org> wrote:
>> Hello folks,
>>
>> Given that our last release was in early December, 2013, it seems like a good time to target a new release. I believe most of the critical security related fixes have gone in and the few that remain in TEZ-669 could be targeted for a future release.
>>
>> I have marked a few jiras that could be considered blockers for a 0.3.0 release to ensure good usability ( the list is open for discussion - feel free to add any other issues if you deem them to be blockers ):
>>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20TEZ%20AND%20resolution%20%3D%20Unresolved%20AND%20priority%20%3D%20Blocker%20ORDER%20BY%20key%20DESC
>>
>> Once, these fixes go in, I can aim to make a release sometime next week.
>>
>> Comments/concerns/suggestions?
>>
>> thanks
>> -- Hitesh
>>
>>
>>
>>
>>
>
>
>
> --
> - Tsuyoshi
Re: [DISCUSS] Targeting a 0.3.0-incubating release
Posted by Tsuyoshi OZAWA <oz...@gmail.com>.
Hi,
About 0.3 release itself, LGTM :-) Let's go ahead.
One my question is how to collaborate with application
developers like Hive or Pig project.
Should these developers be recommended to upgrade
from 0.2 to 0.3?
We should clarify the polity against the application developers
though I know Tez is in alpha stage. What do you think?
Thanks, Tsuyoshi
On Fri, Feb 14, 2014 at 2:53 PM, Hitesh Shah <hi...@apache.org> wrote:
> Hello folks,
>
> Given that our last release was in early December, 2013, it seems like a good time to target a new release. I believe most of the critical security related fixes have gone in and the few that remain in TEZ-669 could be targeted for a future release.
>
> I have marked a few jiras that could be considered blockers for a 0.3.0 release to ensure good usability ( the list is open for discussion - feel free to add any other issues if you deem them to be blockers ):
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20TEZ%20AND%20resolution%20%3D%20Unresolved%20AND%20priority%20%3D%20Blocker%20ORDER%20BY%20key%20DESC
>
> Once, these fixes go in, I can aim to make a release sometime next week.
>
> Comments/concerns/suggestions?
>
> thanks
> -- Hitesh
>
>
>
>
>
--
- Tsuyoshi
Re: [DISCUSS] Targeting a 0.3.0-incubating release
Posted by Tsuyoshi OZAWA <oz...@gmail.com>.
Hi,
About 0.3 release itself, LGTM :-) Let's go ahead.
One my question is how to collaborate with application
developers like Hive or Pig project.
Should these developers be recommended to upgrade
from 0.2 to 0.3?
We should clarify the polity against the application developers
though I know Tez is in alpha stage. What do you think?
Thanks, Tsuyoshi
On Fri, Feb 14, 2014 at 2:53 PM, Hitesh Shah <hi...@apache.org> wrote:
> Hello folks,
>
> Given that our last release was in early December, 2013, it seems like a good time to target a new release. I believe most of the critical security related fixes have gone in and the few that remain in TEZ-669 could be targeted for a future release.
>
> I have marked a few jiras that could be considered blockers for a 0.3.0 release to ensure good usability ( the list is open for discussion - feel free to add any other issues if you deem them to be blockers ):
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20TEZ%20AND%20resolution%20%3D%20Unresolved%20AND%20priority%20%3D%20Blocker%20ORDER%20BY%20key%20DESC
>
> Once, these fixes go in, I can aim to make a release sometime next week.
>
> Comments/concerns/suggestions?
>
> thanks
> -- Hitesh
>
>
>
>
>
--
- Tsuyoshi
Re: [DISCUSS] Targeting a 0.3.0-incubating release
Posted by Hitesh Shah <hi...@apache.org>.
Folks,
Just to be clear, I haven't called a vote yet :)
Looks like we have pretty much all of the blockers fixed. Thanks for all your contributions. I will go ahead and create a RC and call a vote soon barring any new blockers.
thanks
-- Hitesh
On Feb 21, 2014, at 10:58 AM, Tsuyoshi OZAWA wrote:
> +1 non-binding. All tests passed in my local environment.
>
> Thanks,
> - Tsuyoshi
>
> On Thu, Feb 20, 2014 at 5:57 PM, Lianhui Wang <li...@gmail.com> wrote:
>> +1 non-binding
>>
>>
>> 2014-02-21 9:18 GMT+08:00 Gunther Hagleitner <gh...@hortonworks.com>:
>>
>>> +1
>>>
>>> Thanks,
>>> Gunther.
>>>
>>>
>>> On Thu, Feb 20, 2014 at 4:58 PM, Bikas Saha <bi...@hortonworks.com> wrote:
>>>
>>>> +1. All outstanding blockers are resolved now.
>>>>
>>>> -----Original Message-----
>>>> From: Hitesh Shah [mailto:hitesh@apache.org]
>>>> Sent: Friday, February 14, 2014 2:54 PM
>>>> To: dev@tez.incubator.apache.org
>>>> Cc: user@tez.incubator.apache.org
>>>> Subject: [DISCUSS] Targeting a 0.3.0-incubating release
>>>>
>>>> Hello folks,
>>>>
>>>> Given that our last release was in early December, 2013, it seems like a
>>>> good time to target a new release. I believe most of the critical
>>> security
>>>> related fixes have gone in and the few that remain in TEZ-669 could be
>>>> targeted for a future release.
>>>>
>>>> I have marked a few jiras that could be considered blockers for a 0.3.0
>>>> release to ensure good usability ( the list is open for discussion - feel
>>>> free to add any other issues if you deem them to be blockers ):
>>>>
>>>>
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20TEZ%20AND%20res
>>>>
>>> olution%20%3D%20Unresolved%20AND%20priority%20%3D%20Blocker%20ORDER%20BY%2
>>>> 0key%20DESC
>>>>
>>>> Once, these fixes go in, I can aim to make a release sometime next week.
>>>>
>>>> Comments/concerns/suggestions?
>>>>
>>>> thanks
>>>> -- Hitesh
>>>>
>>>> --
>>>> 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.
>>>
>>
>>
>>
>> --
>> thanks
>>
>> 王联辉(Lianhui Wang)
>> blog; http://blog.csdn.net/lance_123
>> 兴趣方向：数据库，分布式，数据挖掘，编程语言，互联网技术等
>
>
>
> --
> - Tsuyoshi
Re: [DISCUSS] Targeting a 0.3.0-incubating release
Posted by Hitesh Shah <hi...@apache.org>.
Folks,
Just to be clear, I haven't called a vote yet :)
Looks like we have pretty much all of the blockers fixed. Thanks for all your contributions. I will go ahead and create a RC and call a vote soon barring any new blockers.
thanks
-- Hitesh
On Feb 21, 2014, at 10:58 AM, Tsuyoshi OZAWA wrote:
> +1 non-binding. All tests passed in my local environment.
>
> Thanks,
> - Tsuyoshi
>
> On Thu, Feb 20, 2014 at 5:57 PM, Lianhui Wang <li...@gmail.com> wrote:
>> +1 non-binding
>>
>>
>> 2014-02-21 9:18 GMT+08:00 Gunther Hagleitner <gh...@hortonworks.com>:
>>
>>> +1
>>>
>>> Thanks,
>>> Gunther.
>>>
>>>
>>> On Thu, Feb 20, 2014 at 4:58 PM, Bikas Saha <bi...@hortonworks.com> wrote:
>>>
>>>> +1. All outstanding blockers are resolved now.
>>>>
>>>> -----Original Message-----
>>>> From: Hitesh Shah [mailto:hitesh@apache.org]
>>>> Sent: Friday, February 14, 2014 2:54 PM
>>>> To: dev@tez.incubator.apache.org
>>>> Cc: user@tez.incubator.apache.org
>>>> Subject: [DISCUSS] Targeting a 0.3.0-incubating release
>>>>
>>>> Hello folks,
>>>>
>>>> Given that our last release was in early December, 2013, it seems like a
>>>> good time to target a new release. I believe most of the critical
>>> security
>>>> related fixes have gone in and the few that remain in TEZ-669 could be
>>>> targeted for a future release.
>>>>
>>>> I have marked a few jiras that could be considered blockers for a 0.3.0
>>>> release to ensure good usability ( the list is open for discussion - feel
>>>> free to add any other issues if you deem them to be blockers ):
>>>>
>>>>
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20TEZ%20AND%20res
>>>>
>>> olution%20%3D%20Unresolved%20AND%20priority%20%3D%20Blocker%20ORDER%20BY%2
>>>> 0key%20DESC
>>>>
>>>> Once, these fixes go in, I can aim to make a release sometime next week.
>>>>
>>>> Comments/concerns/suggestions?
>>>>
>>>> thanks
>>>> -- Hitesh
>>>>
>>>> --
>>>> 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.
>>>
>>
>>
>>
>> --
>> thanks
>>
>> 王联辉(Lianhui Wang)
>> blog; http://blog.csdn.net/lance_123
>> 兴趣方向：数据库，分布式，数据挖掘，编程语言，互联网技术等
>
>
>
> --
> - Tsuyoshi
Re: [DISCUSS] Targeting a 0.3.0-incubating release
Posted by Tsuyoshi OZAWA <oz...@gmail.com>.
+1 non-binding. All tests passed in my local environment.
Thanks,
- Tsuyoshi
On Thu, Feb 20, 2014 at 5:57 PM, Lianhui Wang <li...@gmail.com> wrote:
> +1 non-binding
>
>
> 2014-02-21 9:18 GMT+08:00 Gunther Hagleitner <gh...@hortonworks.com>:
>
>> +1
>>
>> Thanks,
>> Gunther.
>>
>>
>> On Thu, Feb 20, 2014 at 4:58 PM, Bikas Saha <bi...@hortonworks.com> wrote:
>>
>> > +1. All outstanding blockers are resolved now.
>> >
>> > -----Original Message-----
>> > From: Hitesh Shah [mailto:hitesh@apache.org]
>> > Sent: Friday, February 14, 2014 2:54 PM
>> > To: dev@tez.incubator.apache.org
>> > Cc: user@tez.incubator.apache.org
>> > Subject: [DISCUSS] Targeting a 0.3.0-incubating release
>> >
>> > Hello folks,
>> >
>> > Given that our last release was in early December, 2013, it seems like a
>> > good time to target a new release. I believe most of the critical
>> security
>> > related fixes have gone in and the few that remain in TEZ-669 could be
>> > targeted for a future release.
>> >
>> > I have marked a few jiras that could be considered blockers for a 0.3.0
>> > release to ensure good usability ( the list is open for discussion - feel
>> > free to add any other issues if you deem them to be blockers ):
>> >
>> >
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20TEZ%20AND%20res
>> >
>> olution%20%3D%20Unresolved%20AND%20priority%20%3D%20Blocker%20ORDER%20BY%2
>> > 0key%20DESC
>> >
>> > Once, these fixes go in, I can aim to make a release sometime next week.
>> >
>> > Comments/concerns/suggestions?
>> >
>> > thanks
>> > -- Hitesh
>> >
>> > --
>> > 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.
>>
>
>
>
> --
> thanks
>
> 王联辉(Lianhui Wang)
> blog; http://blog.csdn.net/lance_123
> 兴趣方向：数据库，分布式，数据挖掘，编程语言，互联网技术等
--
- Tsuyoshi
Re: [DISCUSS] Targeting a 0.3.0-incubating release
Posted by Tsuyoshi OZAWA <oz...@gmail.com>.
+1 non-binding. All tests passed in my local environment.
Thanks,
- Tsuyoshi
On Thu, Feb 20, 2014 at 5:57 PM, Lianhui Wang <li...@gmail.com> wrote:
> +1 non-binding
>
>
> 2014-02-21 9:18 GMT+08:00 Gunther Hagleitner <gh...@hortonworks.com>:
>
>> +1
>>
>> Thanks,
>> Gunther.
>>
>>
>> On Thu, Feb 20, 2014 at 4:58 PM, Bikas Saha <bi...@hortonworks.com> wrote:
>>
>> > +1. All outstanding blockers are resolved now.
>> >
>> > -----Original Message-----
>> > From: Hitesh Shah [mailto:hitesh@apache.org]
>> > Sent: Friday, February 14, 2014 2:54 PM
>> > To: dev@tez.incubator.apache.org
>> > Cc: user@tez.incubator.apache.org
>> > Subject: [DISCUSS] Targeting a 0.3.0-incubating release
>> >
>> > Hello folks,
>> >
>> > Given that our last release was in early December, 2013, it seems like a
>> > good time to target a new release. I believe most of the critical
>> security
>> > related fixes have gone in and the few that remain in TEZ-669 could be
>> > targeted for a future release.
>> >
>> > I have marked a few jiras that could be considered blockers for a 0.3.0
>> > release to ensure good usability ( the list is open for discussion - feel
>> > free to add any other issues if you deem them to be blockers ):
>> >
>> >
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20TEZ%20AND%20res
>> >
>> olution%20%3D%20Unresolved%20AND%20priority%20%3D%20Blocker%20ORDER%20BY%2
>> > 0key%20DESC
>> >
>> > Once, these fixes go in, I can aim to make a release sometime next week.
>> >
>> > Comments/concerns/suggestions?
>> >
>> > thanks
>> > -- Hitesh
>> >
>> > --
>> > 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.
>>
>
>
>
> --
> thanks
>
> 王联辉(Lianhui Wang)
> blog; http://blog.csdn.net/lance_123
> 兴趣方向：数据库，分布式，数据挖掘，编程语言，互联网技术等
--
- Tsuyoshi
Re: [DISCUSS] Targeting a 0.3.0-incubating release
Posted by Lianhui Wang <li...@gmail.com>.
+1 non-binding
2014-02-21 9:18 GMT+08:00 Gunther Hagleitner <gh...@hortonworks.com>:
> +1
>
> Thanks,
> Gunther.
>
>
> On Thu, Feb 20, 2014 at 4:58 PM, Bikas Saha <bi...@hortonworks.com> wrote:
>
> > +1. All outstanding blockers are resolved now.
> >
> > -----Original Message-----
> > From: Hitesh Shah [mailto:hitesh@apache.org]
> > Sent: Friday, February 14, 2014 2:54 PM
> > To: dev@tez.incubator.apache.org
> > Cc: user@tez.incubator.apache.org
> > Subject: [DISCUSS] Targeting a 0.3.0-incubating release
> >
> > Hello folks,
> >
> > Given that our last release was in early December, 2013, it seems like a
> > good time to target a new release. I believe most of the critical
> security
> > related fixes have gone in and the few that remain in TEZ-669 could be
> > targeted for a future release.
> >
> > I have marked a few jiras that could be considered blockers for a 0.3.0
> > release to ensure good usability ( the list is open for discussion - feel
> > free to add any other issues if you deem them to be blockers ):
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20TEZ%20AND%20res
> >
> olution%20%3D%20Unresolved%20AND%20priority%20%3D%20Blocker%20ORDER%20BY%2
> > 0key%20DESC
> >
> > Once, these fixes go in, I can aim to make a release sometime next week.
> >
> > Comments/concerns/suggestions?
> >
> > thanks
> > -- Hitesh
> >
> > --
> > 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.
>
--
thanks
王联辉(Lianhui Wang)
blog; http://blog.csdn.net/lance_123
兴趣方向：数据库，分布式，数据挖掘，编程语言，互联网技术等
Re: [DISCUSS] Targeting a 0.3.0-incubating release
Posted by Gunther Hagleitner <gh...@hortonworks.com>.
+1
Thanks,
Gunther.
On Thu, Feb 20, 2014 at 4:58 PM, Bikas Saha <bi...@hortonworks.com> wrote:
> +1. All outstanding blockers are resolved now.
>
> -----Original Message-----
> From: Hitesh Shah [mailto:hitesh@apache.org]
> Sent: Friday, February 14, 2014 2:54 PM
> To: dev@tez.incubator.apache.org
> Cc: user@tez.incubator.apache.org
> Subject: [DISCUSS] Targeting a 0.3.0-incubating release
>
> Hello folks,
>
> Given that our last release was in early December, 2013, it seems like a
> good time to target a new release. I believe most of the critical security
> related fixes have gone in and the few that remain in TEZ-669 could be
> targeted for a future release.
>
> I have marked a few jiras that could be considered blockers for a 0.3.0
> release to ensure good usability ( the list is open for discussion - feel
> free to add any other issues if you deem them to be blockers ):
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20TEZ%20AND%20res
> olution%20%3D%20Unresolved%20AND%20priority%20%3D%20Blocker%20ORDER%20BY%2
> 0key%20DESC
>
> Once, these fixes go in, I can aim to make a release sometime next week.
>
> Comments/concerns/suggestions?
>
> thanks
> -- Hitesh
>
> --
> 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: [DISCUSS] Targeting a 0.3.0-incubating release
Posted by Gunther Hagleitner <gh...@hortonworks.com>.
+1
Thanks,
Gunther.
On Thu, Feb 20, 2014 at 4:58 PM, Bikas Saha <bi...@hortonworks.com> wrote:
> +1. All outstanding blockers are resolved now.
>
> -----Original Message-----
> From: Hitesh Shah [mailto:hitesh@apache.org]
> Sent: Friday, February 14, 2014 2:54 PM
> To: dev@tez.incubator.apache.org
> Cc: user@tez.incubator.apache.org
> Subject: [DISCUSS] Targeting a 0.3.0-incubating release
>
> Hello folks,
>
> Given that our last release was in early December, 2013, it seems like a
> good time to target a new release. I believe most of the critical security
> related fixes have gone in and the few that remain in TEZ-669 could be
> targeted for a future release.
>
> I have marked a few jiras that could be considered blockers for a 0.3.0
> release to ensure good usability ( the list is open for discussion - feel
> free to add any other issues if you deem them to be blockers ):
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20TEZ%20AND%20res
> olution%20%3D%20Unresolved%20AND%20priority%20%3D%20Blocker%20ORDER%20BY%2
> 0key%20DESC
>
> Once, these fixes go in, I can aim to make a release sometime next week.
>
> Comments/concerns/suggestions?
>
> thanks
> -- Hitesh
>
> --
> 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: [DISCUSS] Targeting a 0.3.0-incubating release
Posted by Bikas Saha <bi...@hortonworks.com>.
+1. All outstanding blockers are resolved now.
-----Original Message-----
From: Hitesh Shah [mailto:hitesh@apache.org]
Sent: Friday, February 14, 2014 2:54 PM
To: dev@tez.incubator.apache.org
Cc: user@tez.incubator.apache.org
Subject: [DISCUSS] Targeting a 0.3.0-incubating release
Hello folks,
Given that our last release was in early December, 2013, it seems like a
good time to target a new release. I believe most of the critical security
related fixes have gone in and the few that remain in TEZ-669 could be
targeted for a future release.
I have marked a few jiras that could be considered blockers for a 0.3.0
release to ensure good usability ( the list is open for discussion - feel
free to add any other issues if you deem them to be blockers ):
https://issues.apache.org/jira/issues/?jql=project%20%3D%20TEZ%20AND%20res
olution%20%3D%20Unresolved%20AND%20priority%20%3D%20Blocker%20ORDER%20BY%2
0key%20DESC
Once, these fixes go in, I can aim to make a release sometime next week.
Comments/concerns/suggestions?
thanks
-- Hitesh
--
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: [DISCUSS] Targeting a 0.3.0-incubating release
Posted by Bikas Saha <bi...@hortonworks.com>.
+1. All outstanding blockers are resolved now.
-----Original Message-----
From: Hitesh Shah [mailto:hitesh@apache.org]
Sent: Friday, February 14, 2014 2:54 PM
To: dev@tez.incubator.apache.org
Cc: user@tez.incubator.apache.org
Subject: [DISCUSS] Targeting a 0.3.0-incubating release
Hello folks,
Given that our last release was in early December, 2013, it seems like a
good time to target a new release. I believe most of the critical security
related fixes have gone in and the few that remain in TEZ-669 could be
targeted for a future release.
I have marked a few jiras that could be considered blockers for a 0.3.0
release to ensure good usability ( the list is open for discussion - feel
free to add any other issues if you deem them to be blockers ):
https://issues.apache.org/jira/issues/?jql=project%20%3D%20TEZ%20AND%20res
olution%20%3D%20Unresolved%20AND%20priority%20%3D%20Blocker%20ORDER%20BY%2
0key%20DESC
Once, these fixes go in, I can aim to make a release sometime next week.
Comments/concerns/suggestions?
thanks
-- Hitesh
--
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.