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 <wangwe...@huawei.com> wrote:

> Good News,   *Any release plan for hive 1.3*  ???
>
> ------------------------------
> Wangwenli
>
>
> *From:* Gopal Vijayaraghavan <go...@hortonworks.com>
> *Date:* 2015-11-14 14:21
> *To:* dev@hive.apache.org
> *CC:* u...@hive.apache.org
> *Subject:* Re: [VOTE] Hive 2.0 release plan
>
> (+user@)
>
> +1.
>
> Cheers,
> Gopal
>
> On 11/13/15, 5:54 PM, "Lefty Leverenz" <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>
> >> > 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.
> >> >>
> >> >>
> >>
>
>
>

Reply via email to