I would like to be proactive about board feedback so I will put up a patch for our site and documentation that describes the status of our active code lines in the terms that Nick suggests below. I would add an entry for 2.0 describing it as "future, unstable".
I would also like to find a service for taking free surveys (or low cost) and advertise a multiple choice survey on dev@ and user@ and Twitter asking users: - What version of HBase do you currently use? (0.94, 0.98, 1.0, 1.1, 1.2). - What version of HBase would you consider upgrading to in the next year? (1.1, 1.2, 1.3, 2.0) This should work for both Apache releases and any derivatives based on a particular minor, and I think we want that usage in aggregate. > On Jul 22, 2016, at 6:42 PM, Nick Dimiduk <[email protected]> wrote: > > Maybe it's worth spelling out? It will become more obvious once 0.98 is > retired. I think of them like this: > > 0.98.x -- legacy > 1.x -- current > > Within current, we have > > 1.0.x -- retired/EOL > 1.1.x -- maintenance > 1.2.x -- stable > 1.3.x -- unstable > > In time, 1.1 will also retire/EOL, 1.2 will become maintenance, and so on. > >> On Friday, July 22, 2016, Andrew Purtell <[email protected]> wrote: >> >> In our last board report we mentioned the several code lines we current >> manage and were asked to consider some form of support policy so the >> community is able to make informed decisions about which release line to >> use. >> >> The first question is: should we have one? >> >> The second question, if the answer to the first is 'yes', is what that >> policy should be. >> >> >> >> >> -- >> Best regards, >> >> - Andy >> >> Problems worthy of attack prove their worth by hitting back. - Piet Hein >> (via Tom White) >>
