Along the same lines as HBase, it seems fine to discontinue old code lines until such point as there is someone willing to maintain a given line - a new RM. Essentially, its the same as an RM stepping down from managing a release and no releases happening until someone cares enough to make a new one.
That said, if there are any users who want to step up and help maintain a release that is no longer managed (ie. b/c you are running an older version and can't upgrade) that would be fantastic. On Fri, Sep 18, 2015 at 5:53 PM James Taylor <[email protected]> wrote: > +user list > > Please let us know if you're counting on HBase 1.0 support given that we > have HBase 1.1 support. > > Thanks, > James > > On Fri, Sep 18, 2015 at 4:11 PM, Nick Dimiduk <[email protected]> wrote: > > > Seems like a better question for the users mailing list. Probably it > > depends on where the vendors are going, if there will be a long-running > > 1.0.x release line, we should keep it around. From Apache perspective, > it's > > probably fine to drop 1.0.x in favor of 1.1.x. HBase 1.2 is right around > > the corner too... > > > > On Thu, Sep 17, 2015 at 4:42 PM, James Taylor <[email protected]> > > wrote: > > > > > Given that we have Phoenix support for HBase 1.1, does anyone feel like > > we > > > need to continue with Phoenix releases for HBase 1.0? > > > > > > Thanks, > > > James > > > > > >
