I am planning to branch tomorrow morning. Is there anything else pressing
that needs to be done? If so, let me know.

On Thu, Jun 6, 2019 at 3:32 PM Grant Henke <[email protected]> wrote:

> We have time for release notes, they can be done early next week.
>
> On Thu, Jun 6, 2019 at 3:31 PM Mike Percy <[email protected]> wrote:
>
>> +1 on another release -- thanks for volunteering to RM Grant, and for
>> putting together the release notes doc.
>>
>> Branching tomorrow sounds good. Frankly I might not be able to add release
>> notes by tomorrow, might need a little more time for that.
>>
>> Mike
>>
>> On Thu, Jun 6, 2019 at 7:31 AM Grant Henke <[email protected]>
>> wrote:
>>
>> > I've created a Google doc to collect 1.10.0 release notes:
>> >
>> >
>> https://docs.google.com/document/d/1CnGvoOob9H8BcY5dPciYCW5RTj9J--wXPmeMDQzqH6Y/edit?usp=sharing
>> >
>> > I listed some notable changes that I think are worth adding release
>> notes
>> > for. If you have context, please fill them out. Also feel free to add
>> > anything else that you think is worth documenting.
>> >
>> > Thank you,
>> > Grant
>> >
>> > On Mon, Jun 3, 2019 at 11:28 AM Grant Henke <[email protected]>
>> wrote:
>> >
>> > > Hello Kudu developers!
>> > >
>> > > It's been just around three months since we released 1.9.0. In that
>> time,
>> > > we've accrued some important improvements and bug fixes (around 337
>> > commits
>> > > since Kudu 1.9.0!). By our usual three-month release cadence, now
>> seems
>> > > like as good a time as any to start thinking about a Kudu 1.10.0
>> release,
>> > > and I'm volunteering to RM it.
>> > >
>> > > I'm proposing we cut the branch for 1.10.x on Monday, *June 10*, which
>> > > gives
>> > > us a week to prepare, and then we'll start a vote a couple of days
>> after
>> > > that.
>> > >
>> > > If this sound good to you all, please start thinking about and
>> writing up
>> > > release notes for notable changes that have landed in this release,
>> and
>> > get
>> > > them checked in before June 10.
>> > >
>> > > Here's a command you can run to check out roughly what you've been up
>> to
>> > > since Kudu 1.9.0's release:
>> > >
>> > > $ git log b2d95c625dc08f9d8af080bd1b192cc0a3b710b4..master --oneline \
>> > > --graph --no-merges --first-parent --author=<your email address>
>> > >
>> > > Please let me know if you agree with this plan, have comments,
>> questions,
>> > > concerns, etc.
>> > >
>> > > Thanks!
>> > >
>> > > --
>> > > Grant Henke
>> > > Software Engineer | Cloudera
>> > > [email protected] | twitter.com/gchenke | linkedin.com/in/granthenke
>> > >
>> >
>> >
>> > --
>> > Grant Henke
>> > Software Engineer | Cloudera
>> > [email protected] | twitter.com/gchenke | linkedin.com/in/granthenke
>> >
>>
>
>
> --
> Grant Henke
> Software Engineer | Cloudera
> [email protected] | twitter.com/gchenke | linkedin.com/in/granthenke
>


-- 
Grant Henke
Software Engineer | Cloudera
[email protected] | twitter.com/gchenke | linkedin.com/in/granthenke

Reply via email to