Hi Kudu dev community, Apologies for the delay on this release. Given I missed the initial branching target date I would like to propose a new schedule.
I would like to propose to cut the branch for 1.7.x on Monday, March 12th, and to start a vote on RC1 a couple of days after that. I will reach out today for docs of any major improvements since 1.6. Also please be sure to adjust/triage any remaining jiras open for the 1.7.0 release here: https://s.apache.org/your-kudu-1-7-jiras If you have any open pending work that needs to be included in the 1.7 release please let me know as soon as possible. Thank you, Grant On Thu, Feb 22, 2018 at 4:09 PM, Mike Percy <mpe...@apache.org> wrote: > Belated +1 Grant, thanks for volunteering to handle the release! > > Mike > > On Thu, Feb 15, 2018 at 2:42 PM, Grant Henke <ghe...@cloudera.com> wrote: > > > Hi Kudu dev community, > > > > It's been a little over 2 months since release 1.6.0 and we've got a > bunch > > of valuable improvements and bug fixes since (~177 commits). > > Based on our usual 2-month cadence, now looks like a good time to start > > thinking about a Kudu 1.7.0 release. > > > > I'll volunteer to RM this one. I'll also propose to cut the branch for > > 1.7.x > > on Thursday, February 22nd, and to start a vote on RC1 a couple of days > > after that. > > > > Devs: If you have authored any major improvements since 1.6, now is the > > time to > > start writing release note entries, or let me know so I can do that. > > > > Please let me know your thoughts on the above plan. > > > > Thanks, > > Grant > > -- > > Grant Henke > > Software Engineer | Cloudera > > gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke > > > -- Grant Henke Software Engineer | Cloudera gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
