Re: [VOTE] Hive 2.0 release plan

[Sergey Shelukhin]

Yeah I will send an update. There were a few more blockers and now again one 
remains.

From: Hanish Bansal 
mailto:hanish.bansal.agar...@gmail.com>>
Reply-To: "user@hive.apache.org<mailto:user@hive.apache.org>" 
mailto:user@hive.apache.org>>
Date: Tuesday, January 19, 2016 at 22:00
To: "user@hive.apache.org<mailto:user@hive.apache.org>" 
mailto:user@hive.apache.org>>
Subject: Re: [VOTE] Hive 2.0 release plan


Thanks sergey for quick response.

I would request you to update on this group when you cut out RC for 2.0.

Regards,
Hanish Bansal

On 20-Jan-2016 12:21 am, "Sergey Shelukhin" 
mailto:ser...@hortonworks.com>> wrote:
Hi.
There are 2 blockers for Hive 2.0 currently. One is about to be committed, and 
another is in progress, or may be pushed out soon.
I am planning to cut an RC for Hive 2.0 this week.

From: Hanish Bansal 
mailto:hanish.bansal.agar...@gmail.com>>
Reply-To: "user@hive.apache.org<mailto:user@hive.apache.org>" 
mailto:user@hive.apache.org>>
Date: Tuesday, January 19, 2016 at 10:08
To: "user@hive.apache.org<mailto:user@hive.apache.org>" 
mailto:user@hive.apache.org>>
Subject: Re: [VOTE] Hive 2.0 release plan

Hi,

I would like to know any update about release plan for Hive 1.3.0 or 2.0.0 ??

On Tue, Dec 1, 2015 at 12:56 AM, Alan Gates 
mailto:alanfga...@gmail.com>> wrote:
Hive 2.0 will not be 100% backwards compatible with 1.x.  The following JIRA 
link shows JIRAs already committed to 2.0 that break compatibility:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20fixVersion%20%3D%202.0.0%20AND%20%22Hadoop%20Flags%22%20%3D%20%22Incompatible%20change%22

HIVE-12429 is not yet committed but may also make the list.

In summary, the biggest changes are that Hadoop 1.x is no longer supported, 
MapReduce as an engine is deprecated (though still supported for now), and 
HIVE-12429 proposes to switch the standard authorization model to SQL Standard 
Auth instead of the current default.

The goal from the beginning was for 2.0 to be allowed to break compatibility 
where necessary while branch-1 and subsequent 1.x releases would maintain 
backwards compatibility with the 1.x line.

Alan.

[cid:part1.07010802.08040703@gmail.com]
John Omernik<mailto:j...@omernik.com>
November 30, 2015 at 9:25
Agreed, any plans for Hive 1.3?  Will Hive 2.0 be a breaking release for those 
running 1.x?





[cid:part1.07010802.08040703@gmail.com]
Wangwenli<mailto:wangwe...@huawei.com>
November 15, 2015 at 17:07
Good News,   Any release plan for hive 1.3  ???


Wangwenli
[cid:part1.07010802.08040703@gmail.com]
Gopal Vijayaraghavan<mailto:gop...@apache.org>
November 13, 2015 at 22:21

(+user@)

+1.

Cheers,
Gopal

On 11/13/15, 5:54 PM, "Lefty Leverenz" 
<mailto:leftylever...@gmail.com> wrote:



The Hive bylaws require this to be submitted on the user@hive mailing list
(even though users don't get to vote).  See Release Plan in Actions
<https://cwiki.apache.org/confluence/display/Hive/Bylaws#Bylaws-Actions><https://cwiki.apache.org/confluence/display/Hive/Bylaws#Bylaws-Actions>.

-- Lefty


...


On Fri, Nov 13, 2015 at 1:38 PM, Sergey Shelukhin <


ser...@hortonworks.com<mailto:ser...@hortonworks.com>>


wrote:



Hi.
With no strong objections on DISCUSS thread, some issues raised and
addressed, and a reminder from Carl about the bylaws for the release
process, I propose we release the first version of Hive 2 (2.0), and
nominate myself as release manager.
The goal is to have the first release of Hive with aggressive set of


new


features, some of which are ready to use and some are at experimental
stage and will be developed in future Hive 2 releases, in line with


the


Hive-1-Hive-2 split discussion.
If the vote passes, the timeline to create a branch should be around


the


end of next week (to minimize merging in the wake of the release),


and
the


timeline to release would be around the end of November, depending on


the


issues found during the RC cutting process, as usual.

Please vote:
+1 proceed with the release plan
+-0 don¹t care
-1 don¹t proceed with the release plan, for such and such reasons

The vote will run for 3 days.




[cid:part1.07010802.08040703@gmail.com]
Lefty Leverenz<mailto:leftylever...@gmail.com>
November 13, 2015 at 17:54
The Hive bylaws require this to be submitted on the user@hive mailing list
(even though users don't get to vote). See Release Plan in Actions
<https://cwiki.apache.org/confluence/display/Hive/Bylaws#Bylaws-Actions><https://cwiki.apache.org/confluence/display/Hive/Bylaws#Bylaws-Actions>.

-- Lefty


[cid:part1.07010802.08040703@gmail.com]
Thejas Nair<mailto:thejas.n...@gmail.com>
November 13, 2015 at 16:33
+1

On Fri, Nov 13, 2015 at 2:26 PM, Vaibhav Gumashta



--
Thanks & Regards
Hanish Bansal

Re: [VOTE] Hive 2.0 release plan

[Hanish Bansal]

Thanks sergey for quick response.

I would request you to update on this group when you cut out RC for 2.0.

Regards,
Hanish Bansal
On 20-Jan-2016 12:21 am, "Sergey Shelukhin"  wrote:

> Hi.
> There are 2 blockers for Hive 2.0 currently. One is about to be committed,
> and another is in progress, or may be pushed out soon.
> I am planning to cut an RC for Hive 2.0 this week.
>
> From: Hanish Bansal 
> Reply-To: "user@hive.apache.org" 
> Date: Tuesday, January 19, 2016 at 10:08
> To: "user@hive.apache.org" 
> Subject: Re: [VOTE] Hive 2.0 release plan
>
> Hi,
>
> I would like to know any update about release plan for Hive 1.3.0 or 2.0.0
> ??
>
> On Tue, Dec 1, 2015 at 12:56 AM, Alan Gates  wrote:
>
>> Hive 2.0 will not be 100% backwards compatible with 1.x.  The following
>> JIRA link shows JIRAs already committed to 2.0 that break compatibility:
>>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20fixVersion%20%3D%202.0.0%20AND%20%22Hadoop%20Flags%22%20%3D%20%22Incompatible%20change%22
>>
>> HIVE-12429 is not yet committed but may also make the list.
>>
>> In summary, the biggest changes are that Hadoop 1.x is no longer
>> supported, MapReduce as an engine is deprecated (though still supported for
>> now), and HIVE-12429 proposes to switch the standard authorization model to
>> SQL Standard Auth instead of the current default.
>>
>> The goal from the beginning was for 2.0 to be allowed to break
>> compatibility where necessary while branch-1 and subsequent 1.x releases
>> would maintain backwards compatibility with the 1.x line.
>>
>> Alan.
>>
>> John Omernik 
>> November 30, 2015 at 9:25
>> Agreed, any plans for Hive 1.3?  Will Hive 2.0 be a breaking release for
>> those running 1.x?
>>
>>
>>
>>
>>
>> Wangwenli 
>> November 15, 2015 at 17:07
>> Good News,   *Any release plan for hive 1.3*  ???
>>
>> --
>> Wangwenli
>> Gopal Vijayaraghavan 
>> November 13, 2015 at 22:21
>>
>> (+user@)
>>
>> +1.
>>
>> Cheers,
>> Gopal
>>
>> On 11/13/15, 5:54 PM, "Lefty Leverenz"  
>>  wrote:
>>
>>
>> The Hive bylaws require this to be submitted on the user@hive mailing list
>> (even though users don't get to vote).  See Release Plan in 
>> Actions<https://cwiki.apache.org/confluence/display/Hive/Bylaws#Bylaws-Actions>
>>  <https://cwiki.apache.org/confluence/display/Hive/Bylaws#Bylaws-Actions>.
>>
>> -- Lefty
>>
>> ...
>>
>> On Fri, Nov 13, 2015 at 1:38 PM, Sergey Shelukhin <
>>
>> ser...@hortonworks.com>
>>
>> wrote:
>>
>>
>> Hi.
>> With no strong objections on DISCUSS thread, some issues raised and
>> addressed, and a reminder from Carl about the bylaws for the release
>> process, I propose we release the first version of Hive 2 (2.0), and
>> nominate myself as release manager.
>> The goal is to have the first release of Hive with aggressive set of
>>
>> new
>>
>> features, some of which are ready to use and some are at experimental
>> stage and will be developed in future Hive 2 releases, in line with
>>
>> the
>>
>> Hive-1-Hive-2 split discussion.
>> If the vote passes, the timeline to create a branch should be around
>>
>> the
>>
>> end of next week (to minimize merging in the wake of the release),
>>
>> and
>> the
>>
>> timeline to release would be around the end of November, depending on
>>
>> the
>>
>> issues found during the RC cutting process, as usual.
>>
>> Please vote:
>> +1 proceed with the release plan
>> +-0 don¹t care
>> -1 don¹t proceed with the release plan, for such and such reasons
>>
>> The vote will run for 3 days.
>>
>>
>>
>> Lefty Leverenz 
>> November 13, 2015 at 17:54
>> The Hive bylaws require this to be submitted on the user@hive mailing
>> list
>> (even though users don't get to vote). See Release Plan in Actions
>> <https://cwiki.apache.org/confluence/display/Hive/Bylaws#Bylaws-Actions>
>> <https://cwiki.apache.org/confluence/display/Hive/Bylaws#Bylaws-Actions>.
>>
>> -- Lefty
>>
>>
>> Thejas Nair 
>> November 13, 2015 at 16:33
>> +1
>>
>> On Fri, Nov 13, 2015 at 2:26 PM, Vaibhav Gumashta
>>
>>
>
>
> --
> *Thanks & Regards*
> *Hanish Bansal*
>

Re: [VOTE] Hive 2.0 release plan

[Sergey Shelukhin]

Hi.
There are 2 blockers for Hive 2.0 currently. One is about to be committed, and 
another is in progress, or may be pushed out soon.
I am planning to cut an RC for Hive 2.0 this week.

From: Hanish Bansal 
mailto:hanish.bansal.agar...@gmail.com>>
Reply-To: "user@hive.apache.org<mailto:user@hive.apache.org>" 
mailto:user@hive.apache.org>>
Date: Tuesday, January 19, 2016 at 10:08
To: "user@hive.apache.org<mailto:user@hive.apache.org>" 
mailto:user@hive.apache.org>>
Subject: Re: [VOTE] Hive 2.0 release plan

Hi,

I would like to know any update about release plan for Hive 1.3.0 or 2.0.0 ??

On Tue, Dec 1, 2015 at 12:56 AM, Alan Gates 
mailto:alanfga...@gmail.com>> wrote:
Hive 2.0 will not be 100% backwards compatible with 1.x.  The following JIRA 
link shows JIRAs already committed to 2.0 that break compatibility:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20fixVersion%20%3D%202.0.0%20AND%20%22Hadoop%20Flags%22%20%3D%20%22Incompatible%20change%22

HIVE-12429 is not yet committed but may also make the list.

In summary, the biggest changes are that Hadoop 1.x is no longer supported, 
MapReduce as an engine is deprecated (though still supported for now), and 
HIVE-12429 proposes to switch the standard authorization model to SQL Standard 
Auth instead of the current default.

The goal from the beginning was for 2.0 to be allowed to break compatibility 
where necessary while branch-1 and subsequent 1.x releases would maintain 
backwards compatibility with the 1.x line.

Alan.

[cid:part1.07010802.08040703@gmail.com]
John Omernik<mailto:j...@omernik.com>
November 30, 2015 at 9:25
Agreed, any plans for Hive 1.3?  Will Hive 2.0 be a breaking release for those 
running 1.x?





[cid:part1.07010802.08040703@gmail.com]
Wangwenli<mailto:wangwe...@huawei.com>
November 15, 2015 at 17:07
Good News,   Any release plan for hive 1.3  ???


Wangwenli
[cid:part1.07010802.08040703@gmail.com]
Gopal Vijayaraghavan<mailto:gop...@apache.org>
November 13, 2015 at 22:21

(+user@)

+1.

Cheers,
Gopal

On 11/13/15, 5:54 PM, "Lefty Leverenz" 
<mailto:leftylever...@gmail.com> wrote:



The Hive bylaws require this to be submitted on the user@hive mailing list
(even though users don't get to vote).  See Release Plan in Actions
<https://cwiki.apache.org/confluence/display/Hive/Bylaws#Bylaws-Actions><https://cwiki.apache.org/confluence/display/Hive/Bylaws#Bylaws-Actions>.

-- Lefty


...


On Fri, Nov 13, 2015 at 1:38 PM, Sergey Shelukhin <


ser...@hortonworks.com<mailto:ser...@hortonworks.com>>


wrote:



Hi.
With no strong objections on DISCUSS thread, some issues raised and
addressed, and a reminder from Carl about the bylaws for the release
process, I propose we release the first version of Hive 2 (2.0), and
nominate myself as release manager.
The goal is to have the first release of Hive with aggressive set of


new


features, some of which are ready to use and some are at experimental
stage and will be developed in future Hive 2 releases, in line with


the


Hive-1-Hive-2 split discussion.
If the vote passes, the timeline to create a branch should be around


the


end of next week (to minimize merging in the wake of the release),


and
the


timeline to release would be around the end of November, depending on


the


issues found during the RC cutting process, as usual.

Please vote:
+1 proceed with the release plan
+-0 don¹t care
-1 don¹t proceed with the release plan, for such and such reasons

The vote will run for 3 days.




[cid:part1.07010802.08040703@gmail.com]
Lefty Leverenz<mailto:leftylever...@gmail.com>
November 13, 2015 at 17:54
The Hive bylaws require this to be submitted on the user@hive mailing list
(even though users don't get to vote). See Release Plan in Actions
<https://cwiki.apache.org/confluence/display/Hive/Bylaws#Bylaws-Actions><https://cwiki.apache.org/confluence/display/Hive/Bylaws#Bylaws-Actions>.

-- Lefty


[cid:part1.07010802.08040703@gmail.com]
Thejas Nair<mailto:thejas.n...@gmail.com>
November 13, 2015 at 16:33
+1

On Fri, Nov 13, 2015 at 2:26 PM, Vaibhav Gumashta



--
Thanks & Regards
Hanish Bansal

Re: [VOTE] Hive 2.0 release plan

[Hanish Bansal]

Hi,

I would like to know any update about release plan for Hive 1.3.0 or 2.0.0
??

On Tue, Dec 1, 2015 at 12:56 AM, Alan Gates  wrote:

> Hive 2.0 will not be 100% backwards compatible with 1.x.  The following
> JIRA link shows JIRAs already committed to 2.0 that break compatibility:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20fixVersion%20%3D%202.0.0%20AND%20%22Hadoop%20Flags%22%20%3D%20%22Incompatible%20change%22
>
> HIVE-12429 is not yet committed but may also make the list.
>
> In summary, the biggest changes are that Hadoop 1.x is no longer
> supported, MapReduce as an engine is deprecated (though still supported for
> now), and HIVE-12429 proposes to switch the standard authorization model to
> SQL Standard Auth instead of the current default.
>
> The goal from the beginning was for 2.0 to be allowed to break
> compatibility where necessary while branch-1 and subsequent 1.x releases
> would maintain backwards compatibility with the 1.x line.
>
> Alan.
>
> John Omernik 
> November 30, 2015 at 9:25
> Agreed, any plans for Hive 1.3?  Will Hive 2.0 be a breaking release for
> those running 1.x?
>
>
>
>
>
> Wangwenli 
> November 15, 2015 at 17:07
> Good News,   *Any release plan for hive 1.3*  ???
>
> --
> Wangwenli
> Gopal Vijayaraghavan 
> November 13, 2015 at 22:21
>
> (+user@)
>
> +1.
>
> Cheers,
> Gopal
>
> On 11/13/15, 5:54 PM, "Lefty Leverenz"  
>  wrote:
>
>
> The Hive bylaws require this to be submitted on the user@hive mailing list
> (even though users don't get to vote).  See Release Plan in 
> Actions
>  .
>
> -- Lefty
>
> ...
>
> On Fri, Nov 13, 2015 at 1:38 PM, Sergey Shelukhin <
>
> ser...@hortonworks.com>
>
> wrote:
>
>
> Hi.
> With no strong objections on DISCUSS thread, some issues raised and
> addressed, and a reminder from Carl about the bylaws for the release
> process, I propose we release the first version of Hive 2 (2.0), and
> nominate myself as release manager.
> The goal is to have the first release of Hive with aggressive set of
>
> new
>
> features, some of which are ready to use and some are at experimental
> stage and will be developed in future Hive 2 releases, in line with
>
> the
>
> Hive-1-Hive-2 split discussion.
> If the vote passes, the timeline to create a branch should be around
>
> the
>
> end of next week (to minimize merging in the wake of the release),
>
> and
> the
>
> timeline to release would be around the end of November, depending on
>
> the
>
> issues found during the RC cutting process, as usual.
>
> Please vote:
> +1 proceed with the release plan
> +-0 don¹t care
> -1 don¹t proceed with the release plan, for such and such reasons
>
> The vote will run for 3 days.
>
>
>
>  Lefty Leverenz 
> November 13, 2015 at 17:54
> The Hive bylaws require this to be submitted on the user@hive mailing list
> (even though users don't get to vote). See Release Plan in Actions
> 
> .
>
> -- Lefty
>
>
> Thejas Nair 
> November 13, 2015 at 16:33
> +1
>
> On Fri, Nov 13, 2015 at 2:26 PM, Vaibhav Gumashta
>
>


-- 
*Thanks & Regards*
*Hanish Bansal*

Re: [VOTE] Hive 2.0 release plan

[Alan Gates]

Hive 2.0 will not be 100% backwards compatible with 1.x.  The following 
JIRA link shows JIRAs already committed to 2.0 that break compatibility:

https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20fixVersion%20%3D%202.0.0%20AND%20%22Hadoop%20Flags%22%20%3D%20%22Incompatible%20change%22

HIVE-12429 is not yet committed but may also make the list.

In summary, the biggest changes are that Hadoop 1.x is no longer 
supported, MapReduce as an engine is deprecated (though still supported 
for now), and HIVE-12429 proposes to switch the standard authorization 
model to SQL Standard Auth instead of the current default.


The goal from the beginning was for 2.0 to be allowed to break 
compatibility where necessary while branch-1 and subsequent 1.x releases 
would maintain backwards compatibility with the 1.x line.


Alan.


John Omernik 
November 30, 2015 at 9:25
Agreed, any plans for Hive 1.3?  Will Hive 2.0 be a breaking release 
for those running 1.x?






Wangwenli 
November 15, 2015 at 17:07
Good News, *Any release plan for hive 1.3*  ???


Wangwenli
Gopal Vijayaraghavan 
November 13, 2015 at 22:21
(+user@)

+1.

Cheers,
Gopal

On 11/13/15, 5:54 PM, "Lefty Leverenz"  wrote:


The Hive bylaws require this to be submitted on the user@hive mailing list
(even though users don't get to vote).  See Release Plan in Actions
.

-- Lefty

...

On Fri, Nov 13, 2015 at 1:38 PM, Sergey Shelukhin<

ser...@hortonworks.com>

wrote:


Hi.
With no strong objections on DISCUSS thread, some issues raised and
addressed, and a reminder from Carl about the bylaws for the release
process, I propose we release the first version of Hive 2 (2.0), and
nominate myself as release manager.
The goal is to have the first release of Hive with aggressive set of

new

features, some of which are ready to use and some are at experimental
stage and will be developed in future Hive 2 releases, in line with

the

Hive-1-Hive-2 split discussion.
If the vote passes, the timeline to create a branch should be around

the

end of next week (to minimize merging in the wake of the release),

and
the

timeline to release would be around the end of November, depending on

the

issues found during the RC cutting process, as usual.

Please vote:
+1 proceed with the release plan
+-0 don¹t care
-1 don¹t proceed with the release plan, for such and such reasons

The vote will run for 3 days.





Lefty Leverenz 
November 13, 2015 at 17:54
The Hive bylaws require this to be submitted on the user@hive mailing list
(even though users don't get to vote). See Release Plan in Actions
.

-- Lefty


Thejas Nair 
November 13, 2015 at 16:33
+1

On Fri, Nov 13, 2015 at 2:26 PM, Vaibhav Gumashta

Re: [VOTE] Hive 2.0 release plan

[Sergey Shelukhin]

So far there’s no plan for Hive 1.3. If someone from committer (PMC? I don’t 
recall) volunteers they can do the release, should not be difficult, although 
there are some JIRAs that would need backporting I think (I marked them with 
target version recently).

In fact 2.0 branch creation is delayed because we are waiting for replacement 
branch for master :(


From: John Omernik mailto:j...@omernik.com>>
Reply-To: "user@hive.apache.org<mailto:user@hive.apache.org>" 
mailto:user@hive.apache.org>>
Date: Monday, November 30, 2015 at 09:25
To: "user@hive.apache.org<mailto:user@hive.apache.org>" 
mailto:user@hive.apache.org>>
Cc: Gopal Vijayaraghavan mailto:go...@hortonworks.com>>, 
"d...@hive.apache.org<mailto:d...@hive.apache.org>" 
mailto:d...@hive.apache.org>>
Subject: Re: Re: [VOTE] Hive 2.0 release plan

Agreed, any plans for Hive 1.3?  Will Hive 2.0 be a breaking release for those 
running 1.x?




On Sun, Nov 15, 2015 at 7:07 PM, Wangwenli 
mailto:wangwe...@huawei.com>> wrote:
Good News,   Any release plan for hive 1.3  ???


Wangwenli

From: Gopal Vijayaraghavan<mailto:go...@hortonworks.com>
Date: 2015-11-14 14:21
To: d...@hive.apache.org<mailto:d...@hive.apache.org>
CC: user@hive.apache.org<mailto:user@hive.apache.org>
Subject: Re: [VOTE] Hive 2.0 release plan

(+user@)

+1.

Cheers,
Gopal

On 11/13/15, 5:54 PM, "Lefty Leverenz" 
mailto:leftylever...@gmail.com>> wrote:

>The Hive bylaws require this to be submitted on the user@hive mailing list
>(even though users don't get to vote).  See Release Plan in Actions
><https://cwiki.apache.org/confluence/display/Hive/Bylaws#Bylaws-Actions>.
>
>-- Lefty
...
>> > On Fri, Nov 13, 2015 at 1:38 PM, Sergey Shelukhin <
>> ser...@hortonworks.com<mailto:ser...@hortonworks.com>>
>> > wrote:
>> >
>> >> Hi.
>> >> With no strong objections on DISCUSS thread, some issues raised and
>> >> addressed, and a reminder from Carl about the bylaws for the release
>> >> process, I propose we release the first version of Hive 2 (2.0), and
>> >> nominate myself as release manager.
>> >> The goal is to have the first release of Hive with aggressive set of
>>new
>> >> features, some of which are ready to use and some are at experimental
>> >> stage and will be developed in future Hive 2 releases, in line with
>>the
>> >> Hive-1-Hive-2 split discussion.
>> >> If the vote passes, the timeline to create a branch should be around
>>the
>> >> end of next week (to minimize merging in the wake of the release),
>>and
>> the
>> >> timeline to release would be around the end of November, depending on
>> the
>> >> issues found during the RC cutting process, as usual.
>> >>
>> >> Please vote:
>> >> +1 proceed with the release plan
>> >> +-0 don1t care
>> >> -1 don1t proceed with the release plan, for such and such reasons
>> >>
>> >> The vote will run for 3 days.
>> >>
>> >>
>>

Re: Re: [VOTE] Hive 2.0 release plan

[John Omernik]

Agreed, any plans for Hive 1.3?  Will Hive 2.0 be a breaking release for
those running 1.x?




On Sun, Nov 15, 2015 at 7:07 PM, Wangwenli  wrote:

> Good News,   *Any release plan for hive 1.3*  ???
>
> --
> Wangwenli
>
>
> *From:* Gopal Vijayaraghavan 
> *Date:* 2015-11-14 14:21
> *To:* d...@hive.apache.org
> *CC:* user@hive.apache.org
> *Subject:* Re: [VOTE] Hive 2.0 release plan
>
> (+user@)
>
> +1.
>
> Cheers,
> Gopal
>
> On 11/13/15, 5:54 PM, "Lefty Leverenz"  wrote:
>
> >The Hive bylaws require this to be submitted on the user@hive mailing
> list
> >(even though users don't get to vote).  See Release Plan in Actions
> ><https://cwiki.apache.org/confluence/display/Hive/Bylaws#Bylaws-Actions>.
> >
> >-- Lefty
> ...
> >> > On Fri, Nov 13, 2015 at 1:38 PM, Sergey Shelukhin <
> >> ser...@hortonworks.com>
> >> > wrote:
> >> >
> >> >> Hi.
> >> >> With no strong objections on DISCUSS thread, some issues raised and
> >> >> addressed, and a reminder from Carl about the bylaws for the release
> >> >> process, I propose we release the first version of Hive 2 (2.0), and
> >> >> nominate myself as release manager.
> >> >> The goal is to have the first release of Hive with aggressive set of
> >>new
> >> >> features, some of which are ready to use and some are at experimental
> >> >> stage and will be developed in future Hive 2 releases, in line with
> >>the
> >> >> Hive-1-Hive-2 split discussion.
> >> >> If the vote passes, the timeline to create a branch should be around
> >>the
> >> >> end of next week (to minimize merging in the wake of the release),
> >>and
> >> the
> >> >> timeline to release would be around the end of November, depending on
> >> the
> >> >> issues found during the RC cutting process, as usual.
> >> >>
> >> >> Please vote:
> >> >> +1 proceed with the release plan
> >> >> +-0 don1t care
> >> >> -1 don1t proceed with the release plan, for such and such reasons
> >> >>
> >> >> The vote will run for 3 days.
> >> >>
> >> >>
> >>
>
>
>

Re: [VOTE] Hive 2.0 release plan

[Sergey Shelukhin]

Hmm. I looked at the JIRAs targeting the release and it looks like there’s
large number of features still pending.
I am going to postpone creating the branch to next week.
I am also going to unassign JIRAs from the release at that time.

On 15/11/16, 18:09, "Sergey Shelukhin"  wrote:

>With 8 binding +1s and 0 -1s the vote passes.
>The release activities will now proceed according to the plan. I will look
>at the features that are targeted at 2.0 release and create the branch
>~EOW balancing  the waiting for large commits and avoiding too much delay.
>
>On 15/11/16, 10:32, "Sergey Shelukhin"  wrote:
>
>>Including the user list.
>>
>>On 15/11/13, 17:54, "Lefty Leverenz"  wrote:
>>
>>>The Hive bylaws require this to be submitted on the user@hive mailing
>>>list
>>>(even though users don't get to vote).  See Release Plan in Actions
>>>
>>>.
>>>
>>>-- Lefty
>>>
>>>On Fri, Nov 13, 2015 at 7:33 PM, Thejas Nair 
>>>wrote:
>>>
 +1

 On Fri, Nov 13, 2015 at 2:26 PM, Vaibhav Gumashta
  wrote:
 > +1
 >
 > Thanks,
 > --Vaibhav
 >
 >
 >
 >
 >
 > On Fri, Nov 13, 2015 at 2:24 PM -0800, "Tristram de Lyones" <
 delyo...@gmail.com> wrote:
 >
 > +1
 >
 > On Fri, Nov 13, 2015 at 1:38 PM, Sergey Shelukhin <
 ser...@hortonworks.com>
 > wrote:
 >
 >> Hi.
 >> With no strong objections on DISCUSS thread, some issues raised and
 >> addressed, and a reminder from Carl about the bylaws for the
release
 >> process, I propose we release the first version of Hive 2 (2.0),
and
 >> nominate myself as release manager.
 >> The goal is to have the first release of Hive with aggressive set
of
new
 >> features, some of which are ready to use and some are at
experimental
 >> stage and will be developed in future Hive 2 releases, in line with
the
 >> Hive-1-Hive-2 split discussion.
 >> If the vote passes, the timeline to create a branch should be
around
the
 >> end of next week (to minimize merging in the wake of the release),
and
 the
 >> timeline to release would be around the end of November, depending
on
 the
 >> issues found during the RC cutting process, as usual.
 >>
 >> Please vote:
 >> +1 proceed with the release plan
 >> +-0 don’t care
 >> -1 don’t proceed with the release plan, for such and such reasons
 >>
 >> The vote will run for 3 days.
 >>
 >>

>>
>

Re: [VOTE] Hive 2.0 release plan

[Sergey Shelukhin]

With 8 binding +1s and 0 -1s the vote passes.
The release activities will now proceed according to the plan. I will look
at the features that are targeted at 2.0 release and create the branch
~EOW balancing  the waiting for large commits and avoiding too much delay.

On 15/11/16, 10:32, "Sergey Shelukhin"  wrote:

>Including the user list.
>
>On 15/11/13, 17:54, "Lefty Leverenz"  wrote:
>
>>The Hive bylaws require this to be submitted on the user@hive mailing
>>list
>>(even though users don't get to vote).  See Release Plan in Actions
>>.
>>
>>-- Lefty
>>
>>On Fri, Nov 13, 2015 at 7:33 PM, Thejas Nair 
>>wrote:
>>
>>> +1
>>>
>>> On Fri, Nov 13, 2015 at 2:26 PM, Vaibhav Gumashta
>>>  wrote:
>>> > +1
>>> >
>>> > Thanks,
>>> > --Vaibhav
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > On Fri, Nov 13, 2015 at 2:24 PM -0800, "Tristram de Lyones" <
>>> delyo...@gmail.com> wrote:
>>> >
>>> > +1
>>> >
>>> > On Fri, Nov 13, 2015 at 1:38 PM, Sergey Shelukhin <
>>> ser...@hortonworks.com>
>>> > wrote:
>>> >
>>> >> Hi.
>>> >> With no strong objections on DISCUSS thread, some issues raised and
>>> >> addressed, and a reminder from Carl about the bylaws for the release
>>> >> process, I propose we release the first version of Hive 2 (2.0), and
>>> >> nominate myself as release manager.
>>> >> The goal is to have the first release of Hive with aggressive set of
>>>new
>>> >> features, some of which are ready to use and some are at
>>>experimental
>>> >> stage and will be developed in future Hive 2 releases, in line with
>>>the
>>> >> Hive-1-Hive-2 split discussion.
>>> >> If the vote passes, the timeline to create a branch should be around
>>>the
>>> >> end of next week (to minimize merging in the wake of the release),
>>>and
>>> the
>>> >> timeline to release would be around the end of November, depending
>>>on
>>> the
>>> >> issues found during the RC cutting process, as usual.
>>> >>
>>> >> Please vote:
>>> >> +1 proceed with the release plan
>>> >> +-0 don’t care
>>> >> -1 don’t proceed with the release plan, for such and such reasons
>>> >>
>>> >> The vote will run for 3 days.
>>> >>
>>> >>
>>>
>

Re: [VOTE] Hive 2.0 release plan

[Sergey Shelukhin]

Including the user list.

On 15/11/13, 17:54, "Lefty Leverenz"  wrote:

>The Hive bylaws require this to be submitted on the user@hive mailing list
>(even though users don't get to vote).  See Release Plan in Actions
>.
>
>-- Lefty
>
>On Fri, Nov 13, 2015 at 7:33 PM, Thejas Nair 
>wrote:
>
>> +1
>>
>> On Fri, Nov 13, 2015 at 2:26 PM, Vaibhav Gumashta
>>  wrote:
>> > +1
>> >
>> > Thanks,
>> > --Vaibhav
>> >
>> >
>> >
>> >
>> >
>> > On Fri, Nov 13, 2015 at 2:24 PM -0800, "Tristram de Lyones" <
>> delyo...@gmail.com> wrote:
>> >
>> > +1
>> >
>> > On Fri, Nov 13, 2015 at 1:38 PM, Sergey Shelukhin <
>> ser...@hortonworks.com>
>> > wrote:
>> >
>> >> Hi.
>> >> With no strong objections on DISCUSS thread, some issues raised and
>> >> addressed, and a reminder from Carl about the bylaws for the release
>> >> process, I propose we release the first version of Hive 2 (2.0), and
>> >> nominate myself as release manager.
>> >> The goal is to have the first release of Hive with aggressive set of
>>new
>> >> features, some of which are ready to use and some are at experimental
>> >> stage and will be developed in future Hive 2 releases, in line with
>>the
>> >> Hive-1-Hive-2 split discussion.
>> >> If the vote passes, the timeline to create a branch should be around
>>the
>> >> end of next week (to minimize merging in the wake of the release),
>>and
>> the
>> >> timeline to release would be around the end of November, depending on
>> the
>> >> issues found during the RC cutting process, as usual.
>> >>
>> >> Please vote:
>> >> +1 proceed with the release plan
>> >> +-0 don’t care
>> >> -1 don’t proceed with the release plan, for such and such reasons
>> >>
>> >> The vote will run for 3 days.
>> >>
>> >>
>>

Re: [VOTE] Hive 2.0 release plan

[Lefty Leverenz]

+1

(Re-adding user@hive.apache.org.)

-- Lefty

On Sun, Nov 15, 2015 at 8:09 PM, Prasanth Jayachandran <
pjayachand...@hortonworks.com> wrote:

> +1
>
> Thanks
> Prasanth
> > On Nov 13, 2015, at 4:26 PM, Vaibhav Gumashta 
> wrote:
> >
> > +1
> >
> > Thanks,
> > --Vaibhav
> >
> >
> >
> >
> >
> > On Fri, Nov 13, 2015 at 2:24 PM -0800, "Tristram de Lyones" <
> delyo...@gmail.com> wrote:
> >
> > +1
> >
> > On Fri, Nov 13, 2015 at 1:38 PM, Sergey Shelukhin <
> ser...@hortonworks.com>
> > wrote:
> >
> >> Hi.
> >> With no strong objections on DISCUSS thread, some issues raised and
> >> addressed, and a reminder from Carl about the bylaws for the release
> >> process, I propose we release the first version of Hive 2 (2.0), and
> >> nominate myself as release manager.
> >> The goal is to have the first release of Hive with aggressive set of new
> >> features, some of which are ready to use and some are at experimental
> >> stage and will be developed in future Hive 2 releases, in line with the
> >> Hive-1-Hive-2 split discussion.
> >> If the vote passes, the timeline to create a branch should be around the
> >> end of next week (to minimize merging in the wake of the release), and
> the
> >> timeline to release would be around the end of November, depending on
> the
> >> issues found during the RC cutting process, as usual.
> >>
> >> Please vote:
> >> +1 proceed with the release plan
> >> +-0 don’t care
> >> -1 don’t proceed with the release plan, for such and such reasons
> >>
> >> The vote will run for 3 days.
> >>
> >>
>
>
>
> Thanks
> -- Prasanth
>
>

Re: Re: [VOTE] Hive 2.0 release plan

[Wangwenli]

Good News,   Any release plan for hive 1.3  ???


Wangwenli

From: Gopal Vijayaraghavan<mailto:go...@hortonworks.com>
Date: 2015-11-14 14:21
To: d...@hive.apache.org<mailto:d...@hive.apache.org>
CC: user@hive.apache.org<mailto:user@hive.apache.org>
Subject: Re: [VOTE] Hive 2.0 release plan

(+user@)

+1.

Cheers,
Gopal

On 11/13/15, 5:54 PM, "Lefty Leverenz"  wrote:

>The Hive bylaws require this to be submitted on the user@hive mailing list
>(even though users don't get to vote).  See Release Plan in Actions
><https://cwiki.apache.org/confluence/display/Hive/Bylaws#Bylaws-Actions>.
>
>-- Lefty
...
>> > On Fri, Nov 13, 2015 at 1:38 PM, Sergey Shelukhin <
>> ser...@hortonworks.com>
>> > wrote:
>> >
>> >> Hi.
>> >> With no strong objections on DISCUSS thread, some issues raised and
>> >> addressed, and a reminder from Carl about the bylaws for the release
>> >> process, I propose we release the first version of Hive 2 (2.0), and
>> >> nominate myself as release manager.
>> >> The goal is to have the first release of Hive with aggressive set of
>>new
>> >> features, some of which are ready to use and some are at experimental
>> >> stage and will be developed in future Hive 2 releases, in line with
>>the
>> >> Hive-1-Hive-2 split discussion.
>> >> If the vote passes, the timeline to create a branch should be around
>>the
>> >> end of next week (to minimize merging in the wake of the release),
>>and
>> the
>> >> timeline to release would be around the end of November, depending on
>> the
>> >> issues found during the RC cutting process, as usual.
>> >>
>> >> Please vote:
>> >> +1 proceed with the release plan
>> >> +-0 don1t care
>> >> -1 don1t proceed with the release plan, for such and such reasons
>> >>
>> >> The vote will run for 3 days.
>> >>
>> >>
>>

Re: [VOTE] Hive 2.0 release plan

[Gopal Vijayaraghavan]

(+user@)

+1.

Cheers,
Gopal

On 11/13/15, 5:54 PM, "Lefty Leverenz"  wrote:

>The Hive bylaws require this to be submitted on the user@hive mailing list
>(even though users don't get to vote).  See Release Plan in Actions
>.
>
>-- Lefty
...
>> > On Fri, Nov 13, 2015 at 1:38 PM, Sergey Shelukhin <
>> ser...@hortonworks.com>
>> > wrote:
>> >
>> >> Hi.
>> >> With no strong objections on DISCUSS thread, some issues raised and
>> >> addressed, and a reminder from Carl about the bylaws for the release
>> >> process, I propose we release the first version of Hive 2 (2.0), and
>> >> nominate myself as release manager.
>> >> The goal is to have the first release of Hive with aggressive set of
>>new
>> >> features, some of which are ready to use and some are at experimental
>> >> stage and will be developed in future Hive 2 releases, in line with
>>the
>> >> Hive-1-Hive-2 split discussion.
>> >> If the vote passes, the timeline to create a branch should be around
>>the
>> >> end of next week (to minimize merging in the wake of the release),
>>and
>> the
>> >> timeline to release would be around the end of November, depending on
>> the
>> >> issues found during the RC cutting process, as usual.
>> >>
>> >> Please vote:
>> >> +1 proceed with the release plan
>> >> +-0 don¹t care
>> >> -1 don¹t proceed with the release plan, for such and such reasons
>> >>
>> >> The vote will run for 3 days.
>> >>
>> >>
>>