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.
On Fri, Jan 17, 2014 at 4:39 PM, Carl Steinbach <[EMAIL PROTECTED]> 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
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.