Hive 2.0 branch - starting next week, please ask RM before committing (in preparation for the release)

[Sergey Shelukhin <se...@hortonworks.com>]

Hi.
Sorry for the delay, I guess my initial 2.0 timeframe was wildly
optimistic for such a round-numbered release.
As of right now, we only have 2 blockers for Hive 2.0,
https://issues.apache.org/jira/browse/HIVE-12783 which looks like it’s
almost in, and https://issues.apache.org/jira/browse/HIVE-12352 which has
a +1 and needs a HiveQA run.
Once these are in, it’s likely we can get an RC out next week.

Therefore, starting next week, I would like to limit the commits to
branch-2.0 in preparation; please ask for RM (Apache ID: sershe ;))
approval before committing changes to branch-2.0 starting Monday,
2016-01-18.
By default, new features and miscellaneous improvements should go to
master and not branch-2.0 starting then.


Please let me know if
- you think there are other blockers not marked as such;
- you want to get some features/improvements done in 2.0 that are not in
yet.

Re: Hive 2.0 branch - starting next week, please ask RM before committing (in preparation for the release)

[Siddharth Seth <ss...@apache.org>]

I'd like to get the changes under HIVE-12446 committed. The Tez 0.8.2
release is in progress and looks like it'll be available by early next
week. 0.8.2 has some bug fixes, and support for features which allow better
locality for LLAP in Hive 2.0.

Thanks
- Sid

On Thu, Jan 14, 2016 at 11:15 AM, Sergey Shelukhin <se...@hortonworks.com>
wrote:

> Hi.
> Sorry for the delay, I guess my initial 2.0 timeframe was wildly
> optimistic for such a round-numbered release.
> As of right now, we only have 2 blockers for Hive 2.0,
> https://issues.apache.org/jira/browse/HIVE-12783 which looks like it’s
> almost in, and https://issues.apache.org/jira/browse/HIVE-12352 which has
> a +1 and needs a HiveQA run.
> Once these are in, it’s likely we can get an RC out next week.
>
> Therefore, starting next week, I would like to limit the commits to
> branch-2.0 in preparation; please ask for RM (Apache ID: sershe ;))
> approval before committing changes to branch-2.0 starting Monday,
> 2016-01-18.
> By default, new features and miscellaneous improvements should go to
> master and not branch-2.0 starting then.
>
>
> Please let me know if
> - you think there are other blockers not marked as such;
> - you want to get some features/improvements done in 2.0 that are not in
> yet.
>
>