The plan sounds good to me. Thank you for volunteering to RM. Could you create and share a google document similar to ones from past releases where we can start to compile the release notes?
Here is an example: https://docs.google.com/document/d/1CnGvoOob9H8BcY5dPciYCW5RTj9J--wXPmeMDQzqH6Y/edit?usp=sharing Thanks, Grant On Wed, Mar 11, 2020 at 11:16 PM Hao Hao <[email protected]> wrote: > Hello Kudu developers! > > It's been a bit more than three months since we released 1.11.1. In that > time, we've accrued some important improvements and bug fixes (around > 438 commits since Kudu 1.11.0). By our usual three-month release cadence, > now seems like as good a time as any to start thinking about a Kudu 1.12.0 > release, and I'm volunteering to RM it. > > I'm proposing we cut the branch for 1.12.x on Wednesday, *March 18*, > 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 March 18 2020. > > Here's a command you can run to check out roughly what you've been up to > since Kudu 1.11.0 release: > > $ git log 08db97c591d9131cbef9b8e5b4f44a6e854c25f0..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! > Hao > -- Grant Henke Software Engineer | Cloudera [email protected] | twitter.com/gchenke | linkedin.com/in/granthenke
