Hi All,

Sorry about dropping this thread.

I have been looking at 1.2.2 release again (have run precommit tests, gone
over issues with target/fix version of 1.2.2) and as of now there is just
one blocking jira (https://issues.apache.org/jira/browse/HIVE-16247).
Regarding the JSON license header issue pointed out by Alan, as mentioned
in the last comment on https://issues.apache.org/jira/browse/HIVE-15144,
we can still make releases until ~May 2017 while we work on resolving it.

If you have any jiras you¹d like to see into 1.2.2 please mark them as
such, and if possible tag me in the comments. If there are no objections,
I am planning to roll out an RC in the next couple of days.

Thanks,
‹Vaibhav Gumashta

On 11/10/16, 11:27 AM, "Alan Gates" <alanfga...@gmail.com> wrote:

>Note that now that Apache legal has decided that the JSON license is no
>longer acceptable we¹ll have to fix that before we release.  See
>https://issues.apache.org/jira/browse/HIVE-15144 for details.
>
>Alan.
>
>> On Nov 7, 2016, at 02:29, Vaibhav Gumashta <vgumas...@hortonworks.com>
>>wrote:
>> 
>> Hi,
>> 
>> There have been a few bug fixes that have went into the 1.2 branch
>>since 1.2.1 was released (10/14/2015). I have run the pre-commit tests
>>on branch-1.2 and there are 5 failures that I'm evaluating. Other than
>>that, there are about 14 unresolved jiras with target version of 1.2.2
>>or fix version of 1.2.1 which I plan to evaluate in the next couple of
>>days.
>> 
>> If there are no objections, I'd like to cut an RC by end of this week
>>or early next week. If you'd like to land in any critical bug fixes,
>>please feel free to do so (subject to the usual restrictions that apply
>>to a bug fix release: no major changes/db changes/breaking changes).
>> 
>> I'll wait for a couple of days for any response here, and start a vote
>>thread.
>> 
>> Thanks,
>> -Vaibhav Gumashta
>
>

Reply via email to