Sounds good to me, thanks for volunteering.
On Mon, Oct 17, 2016 at 5:27 PM, Jordan Birdsell <jordantbirds...@gmail.com>
> Seems reasonable to me, have a few things for Python left I'd like to get
> in for 1.1: range partition implementation and alter table capabilities,
> that should be enough time.
> Thanks Todd,
> On Mon, Oct 17, 2016, 8:23 PM Todd Lipcon <t...@cloudera.com> wrote:
> > Hey folks,
> > I'd like to propose a release plan for the next few months.
> > My suggestion is that we aim for Kudu 1.1 some time around mid-November
> > hopefully with enough time before Thanksgiving that no one here in the US
> > needs to worry about an impending release over the holiday. So, I think
> > that would be some time the week of 11/14.
> > That gives us a month from now to make some progress on in-flight
> > and fixes. My preference is that this should be a time-based rather than
> > scope-based release, but I expect that some of the items that people are
> > working on should be ready by then. Speaking for myself, the pre-election
> > patch series can improve stability significantly in some cases and it
> > be great to get that out to our users. I'm sure others have improvements
> > pending that will be ready by then too.
> > Following 1.1, I think we should plan for a 1.2 release early in January
> > (6-8 weeks after 1.1). My hope is that we can get a good chunk of the
> > security features that folks have started looking at done by then, as
> > as various other work that people have been circulating design docs for.
> > I'll also volunteer to RM these two releases.
> > Thanks
> > -Todd
> > --
> > Todd Lipcon
> > Software Engineer, Cloudera