hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lefty Leverenz <leftylever...@gmail.com>
Subject Re: Hive 0.14.1 release
Date Wed, 31 Dec 2014 08:12:22 GMT
Oh, now I get it.  The 1.0.0 *branch* of Hive.  Okay.

-- Lefty

On Tue, Dec 30, 2014 at 11:43 PM, Lefty Leverenz <leftyleverenz@gmail.com>
wrote:

> I thought x.x.# releases were just for fixups, x.#.x could include new
> features, and #.x.x were major releases that might have some
> backward-incompatible changes.  But I guess we haven't agreed on that.
>
> As for documentation, we still have 84 jiras with TODOC14 labels
> <https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20labels%20%3D%20TODOC14>.
> Not to mention 25 TODOC13 labels
> <https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20labels%20%3D%20TODOC13>,
> eleven TODOC12
> <https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20labels%20%3D%20TODOC12>,
> seven TODOC11
> <https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20labels%20%3D%20TODOC11>,
> and seven TODOC10
> <https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20labels%20%3D%20TODOC10>
> .
>
> That's 134 doc tasks to finish for a Hive 1.0.0 release -- preferably by
> the release date, not after.  Because expectations are higher for 1.0.0
> releases.
>
>
> -- Lefty
>
> On Tue, Dec 30, 2014 at 5:23 PM, Vikram Dixit K <vikram.dixit@gmail.com>
> wrote:
>
>> Hi Folks,
>>
>> Given that there have been a number of fixes that have gone into branch
>> 0.14 in the past 8 weeks, I would like to make a release of 0.14.1 soon. I
>> would like to fix some of the release issues as well this time around. I
>> am
>> thinking of some time around 15th January for getting a RC out. Please let
>> me know if you have any concerns. Also, from a previous thread, I would
>> like to make this release the 1.0 branch of hive. The process for getting
>> jiras into this release is going to be the same as the previous one viz.:
>>
>> 1. Mark the jira with fix version 0.14.1 and update the status to
>> blocker/critical.
>> 2. If a committer +1s the patch for 0.14.1, it is good to go in. Please
>> mention me in the jira in case you are not sure if the jira should make it
>> for 0.14.1.
>>
>> Thanks
>> Vikram.
>>
>
>

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