hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Navis류승우 <navis....@nexr.com>
Subject Re: Timeline for the Hive 0.13 release?
Date Wed, 05 Feb 2014 04:12:53 GMT
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 this
> > 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 for
> 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 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.
> >
>
>
>
> --
> Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message