yay! what are you looking for in terms of done-ness for inclusion in feature freeze? I think we've got consensus on spark support, for instance, and AFAICT there's only 1-2 issues to close out before it's code complete, both of which have patches.
I was planning to make a summary document of the consensus week after next. Do I need to step that up to get this included in a 1.4 release? It's pretty isolated in the code base. On Fri, Jun 30, 2017 at 4:37 PM, Andrew Purtell <[email protected]> wrote: > Greeting HBasers, > > It's my intention to create a new release branch, branch-1.4, as seed for a > new 1.4.x code line, with a 1.4.0 release coming within the next two > months. > > I would like to volunteer to RM this branch. > > I would like to create the new branch in ASF git, branch-1.4, as early as > next week. > > There are a number of contributions from my colleagues and others that have > been sitting in branch-1 for about a year. As time goes on it will be more > and more difficult to stabilize the current head of branch-1 for release. > There is no time like the present to begin, so let's begin next week! > > If you have concerns, please, let's discuss. (smile) > > > -- > Best regards, > Andrew >
