Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Received-SPF: pass (athena.apache.org: domain of thejas@hortonworks.com
 designates 209.85.219.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CACQ46vHceAyPYxkYoYDX_VmroCYfg74-Fm_N0vQ30Zs3tz6YoQ@mail.gmail.com>
References: 
 <CACf6RrywBtMKsgdTLaq1t+iG+xB6XEK=m07n0VTFqqkrOMay+w@mail.gmail.com>
	<CABgNGzcfFo2jsVg1UVPGW-upsxv+ANHzT_CUG3=FqcaQ0znaSQ@mail.gmail.com>
	<DFCC5CB3-5D9F-4AE1-A7A8-EAB3543C7DA6@hortonworks.com>
	<CAFukC=5oWtwQ6Gg3BiEQ0VV+qQRcjabo1W7s92wPDpUyXWCmoA@mail.gmail.com>
	<CACQ46vHceAyPYxkYoYDX_VmroCYfg74-Fm_N0vQ30Zs3tz6YoQ@mail.gmail.com>
Date: Wed, 5 Feb 2014 21:05:35 -0800
Message-ID: 
 <CABgNGzfhucJkJb04DNH-5Av-vcAPi-_CbBmJy1MzZWz8oVEr_A@mail.gmail.com>
Subject: Re: Timeline for the Hive 0.13 release?
From: Thejas Nair <thejas@hortonworks.com>
To: "dev@hive.apache.org" <dev@hive.apache.org>, navis.ryu@nexr.com
Content-Type: multipart/alternative; boundary=047d7b41904bdfc68a04f1b5d245

--047d7b41904bdfc68a04f1b5d245
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

The Hortonworks folks working in my team on hive are working hard to get
most of the features that are in progress, into hive 0.13. There seems to
be agreement in hive community for branching for stabilization of hive 0.13
around mid Feb.


On Tue, Feb 4, 2014 at 8:12 PM, Navis=EB=A5=98=EC=8A=B9=EC=9A=B0 <navis.ryu=
@nexr.com> wrote:

> Hi all,
>
> We have so much on-going works especially within
> tez/vectorization/authorization territory and they are all under cover of
> Hortonworks. Could anyone in the company to tell whether they have some
> internal milestone for next release?
>
> Thanks,
> Navis
>
>
> 2014-01-21 Brock Noland <brock@cloudera.com>:
>
> > Hi,
> >
> > I agree that picking a date to branch and then restricting commits to
> that
> > branch would be a less time intensive plan for the RM.
> >
> > Brock
> >
> >
> > On Sat, Jan 18, 2014 at 4:21 PM, Harish Butani <hbutani@hortonworks.com
> > >wrote:
> >
> > > Yes agree it is time to start planning for the next release.
> > > I would like to volunteer to do the release management duties for thi=
s
> > > release(will be a great experience for me)
> > > Will be happy to do it, if the community is fine with this.
> > >
> > > regards,
> > > Harish.
> > >
> > > On Jan 17, 2014, at 7:05 PM, Thejas Nair <thejas@hortonworks.com>
> wrote:
> > >
> > > > Yes, I think it is time to start planning for the next release.
> > > > For 0.12 release I created a branch and then accepted patches that
> > > > people asked to be included for sometime, before moving a phase of
> > > > accepting only critical bug fixes. This turned out to be laborious.
> > > > I think we should instead give everyone a few weeks to get any
> patches
> > > > they are working on to be ready, cut the branch, and take in only
> > > > critical bug fixes to the branch after that.
> > > > How about cutting the branch around mid-February and targeting to
> > > > release in a week or two after that.
> > > >
> > > > Thanks,
> > > > Thejas
> > > >
> > > >
> > > > On Fri, Jan 17, 2014 at 4:39 PM, Carl Steinbach <cws@apache.org>
> > wrote:
> > > >> I was wondering what people think about setting a tentative date f=
or
> > the
> > > >> Hive 0.13 release? At an old Hive Contrib meeting we agreed that
> Hive
> > > >> should follow a time-based release model with new releases every
> four
> > > >> months. If we follow that schedule we're due for the next release =
in
> > > >> mid-February.
> > > >>
> > > >> Thoughts?
> > > >>
> > > >> Thanks.
> > > >>
> > > >> Carl
> > > >
> > > > --
> > > > 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 hav=
e
> > > > 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 confidentia=
l,
> > > privileged and exempt from disclosure under applicable law. If the
> reader
> > > of this message is not the intended recipient, you are hereby notifie=
d
> > 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.
> > >
> >
> >
> >
> > --
> > Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org
> >
>

--=20
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to=
=20
which it is addressed and may contain information that is confidential,=20
privileged and exempt from disclosure under applicable law. If the reader=
=20
of this message is not the intended recipient, you are hereby notified that=
=20
any printing, copying, dissemination, distribution, disclosure or=20
forwarding of this communication is strictly prohibited. If you have=20
received this communication in error, please contact the sender immediately=
=20
and delete it from your system. Thank You.

--047d7b41904bdfc68a04f1b5d245--