hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vikram Dixit K <vikram.di...@gmail.com>
Subject Re: Hive 0.14.1 release
Date Fri, 16 Jan 2015 21:35:06 GMT
We seem to already have the jenkins job for that but I could not trigger
that.

http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/HIVE-0.14-HADOOP-2/

Thanks
Vikram.

On Fri, Jan 16, 2015 at 1:33 PM, Vikram Dixit K <vikram.dixit@gmail.com>
wrote:

> Hi Brock/Szehon,
>
> Can you please trigger a unit test run for branch 0.14? I want to get
> started with the release and getting a run over the weekend would be great.
>
> Thanks
> Vikram.
>
> On Thu, Jan 1, 2015 at 10:23 AM, Thejas Nair <thejas@hortonworks.com>
> wrote:
>
>> Yes, 1.0 is a good opportunity to remove some of the deprecated
>> components. The change to remove HiveServer1 is already there in trunk
>> , we should include that.
>> We can also use 1.0 release to clarify the public vs private status of
>> some of the APIs.
>>
>> Thanks for the reminder about the documentation status of 1.0. I will
>> look at some of them.
>>
>>
>> On Wed, Dec 31, 2014 at 12:12 AM, Lefty Leverenz
>> <leftyleverenz@gmail.com> wrote:
>> > 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.
>> >>>
>> >>
>> >>
>>
>> --
>> 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.
>>
>
>
>
> --
> Nothing better than when appreciated for hard work.
> -Mark
>



-- 
Nothing better than when appreciated for hard work.
-Mark

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