+1

On Wed, Oct 2, 2019 at 10:50 AM Grant Henke <[email protected]>
wrote:

> +1
>
> On Tue, Oct 1, 2019 at 4:34 PM Andrew Wong <[email protected]>
> wrote:
>
> > +1
> >
> > Thanks for volunteering, Alexey!
> >
> > On Tue, Oct 1, 2019 at 11:50 AM Adar Lieber-Dembo
> > <[email protected]>
> > wrote:
> >
> > > +1
> > >
> > > On Tue, Oct 1, 2019 at 11:44 AM Alexey Serbin
> > > <[email protected]> wrote:
> > > >
> > > > Hello Kudu developers!
> > > >
> > > > It's been a bit more than three months since we released 1.10.0. In
> > that
> > > > time,
> > > > we've accrued some important improvements and bug fixes (around 189
> > > commits
> > > > since Kudu 1.10.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.11.x on Wednesday, *October 9*,
> > > > 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 October 9 2019.
> > > >
> > > > Here's a command you can run to check out roughly what you've been up
> > to
> > > > since Kudu 1.10.0 release:
> > > >
> > > > $ git log d75a77081326d2f2e7c4d10bc06afb0b39d2c0a2..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!
> > > >
> > > > --
> > > > Alexey Serbin
> > > > Software Engineer | Cloudera
> > >
> >
> >
> > --
> > Andrew Wong
> >
>
>
> --
> Grant Henke
> Software Engineer | Cloudera
> [email protected] | twitter.com/gchenke | linkedin.com/in/granthenke
>

Reply via email to