Re: Kudu 1.6.x branching Tue eve, RC1 on Thu

[Mike Percy <mp...@apache.org>]

Hi folks,
I'm delaying 1.6.0-RC1 for at least one day after we discovered a couple
issues during testing.

The issues in question were introduced during the 1.6.0 development cycle
and are being tracked as KUDU-2229
<https://issues.apache.org/jira/browse/KUDU-2229> and KUDU-2230
<https://issues.apache.org/jira/browse/KUDU-2230>. Alexey and I are
currently working on fixes for both. I'll either start the vote on RC1
tomorrow after the fixes are in or I'll send out another mail with the
latest news on the RC.

Thanks for your patience,
Mike

On Wed, Nov 29, 2017 at 10:55 PM, Mike Percy <mp...@apache.org> wrote:

> Hi folks,
> I've branched for 1.6.0 (a day late) and I'm still planning on spinning
> 1.6.0-RC1 tomorrow (Thursday).
>
> We've included Andrew's disk failure patches (enabled by default) but we
> are not shipping improved re-replication (KUDU-1097) enabled for this
> release.
>
> Because 1.6.x has branched, please add me as a reviewer for anything that
> needs to get in for RC1 at the last minute, such as release notes.
>
> Thanks,
> Mike
>
>
> On Tue, Nov 28, 2017 at 2:51 PM, Mike Percy <mp...@apache.org> wrote:
>
>> Hi all,
>>
>> I just wanted to give an update on the Kudu 1.6 release plan.
>>
>> We have a few outstanding patches that I'd like to see go in for the 1.6
>> release:
>> - Tests from Andrew related to disk failure handling
>> - Wrap-up on improved re-replication from Alexey and I. We'll make a call
>> tomorrow (Wed) on whether to ship this enabled or disabled for Kudu 1.6.0.
>>
>> My plan is to branch in the evening tonight and cut an RC1 on Thu. That
>> will give us about a week of solid testing time from branch to final vote
>> tally, since we'll have the weekend plus a couple weekdays to vote, and if
>> we don't find any issues with RC1 then it will become Kudu 1.6.0 mid next
>> week.
>>
>> If you have not sent me release notes for work you did during this
>> release cycle, please write them up ASAP and send them to me.
>>
>> Please let me know if you have any concerns with this plan or any
>> suggestions.
>>
>> Thanks!
>> Mike
>>
>>
>