Thanks folks. To be clear, I'm willing to fix the release notes without a
new RC, but adding the missing LICENSE requires adding HADOOP-14018 which
changes the checksum of that jar and also the tarballs.

Chris and Karthik, could you clarify the contingency of your votes? Is
fixing just the release notes sufficient?

Thanks,
Andrew

On Wed, Jan 25, 2017 at 11:14 AM, Karthik Kambatla <ka...@cloudera.com>
wrote:

> Thanks for driving the alphas, Andrew. I don't see the need to restart the
> vote and I feel it is okay to fix the minor issues before releasing.
>
> +1 (binding). Downloaded source, stood up a pseudo-distributed cluster
> with FairScheduler, ran example jobs, and played around with the UI.
>
> Thanks
> Karthik
>
>
> On Fri, Jan 20, 2017 at 2:36 PM, Andrew Wang <andrew.w...@cloudera.com>
> wrote:
>
>> Hi all,
>>
>> With heartfelt thanks to many contributors, the RC0 for 3.0.0-alpha2 is
>> ready.
>>
>> 3.0.0-alpha2 is the second alpha in the planned 3.0.0 release line leading
>> up to a 3.0.0 GA. It comprises 857 fixes, improvements, and new features
>> since alpha1 was released on September 3rd, 2016.
>>
>> More information about the 3.0.0 release plan can be found here:
>>
>> https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+3.0.0+release
>>
>> The artifacts can be found here:
>>
>> http://home.apache.org/~wang/3.0.0-alpha2-RC0/
>>
>> This vote will run 5 days, ending on 01/25/2017 at 2PM pacific.
>>
>> I ran basic validation with a local pseudo cluster and a Pi job. RAT
>> output
>> was clean.
>>
>> My +1 to start.
>>
>> Thanks,
>> Andrew
>>
>
>

Reply via email to