I have to concur with Enis here; I wouldn't feel great about dropping
1.{0,1} support in 4.8 since it went out the door like that.
Granted, I don't recall reading any official Phoenix compatibility
guidelines as to what *will* be supported between versions, so, the
ability to do it is there.
Obligatory: I do fall rather far to the edge of the compatibility
spectrum when it comes to "never break users on patch releases".
(4.9 is an entirely different story though)
James Taylor wrote:
The "why" would because no one needs. If there are users consuming it, then
I agree.
On Mon, Aug 29, 2016 at 2:55 PM, Enis Söztutar<[email protected]> wrote:
We have explicitly decided to do the 4.8 release supporting all 4 of 0.98,
1.0, 1.1 and 1.2.
Why would we even consider dropping support for patch releases? Having a
policy for keeping the supported hbase branches supported throughout the
patch releases makes the process simpler. Preventing upgrade to 4.8.1 for
HBase-1.0 and HBase-1.1 users will not look good at all.
I think we can decide the base hbase versions on major version boundaries.
Enis
On Thu, Aug 25, 2016 at 1:39 AM, Andrew Purtell<[email protected]>
wrote:
According to the responses received so far on our version usage survey,
HBase 1.1 is the most popular, followed by 1.2, then 0.98.
On Aug 25, 2016, at 12:43 AM, James Taylor<[email protected]>
wrote:
I propose we only continue releases for HBase 0.98 and 1.2, both for
4.8
patch releases as well as 4.9 minor releases.
Thoughts?
