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.
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 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 re
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 upgrad
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 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 mi
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?