(realized I dropped this)

Thanks for the reply, Andrew, on the 4.x releases. No complaints from me about your request.

Meanwhile, I'd like to move forward with the renaming of master -> 4.x-HBase-1.4 and 5.x-HBase-2.0 -> master since there haven't been any objections. Please speak up by EOD if there are concerns.

On 2018/07/12 19:55:41, Andrew Purtell <[email protected]> wrote: > With my work hat on I would request the 4.x line continue for as long as
HBase 1.x does. Probably it would be best if eventually there is only one
active 4.x branch that follows the HBase 1.x minor release progression. So
it would target 1.4 today, then 1.5, then 1.6 (and I'm not sure there will
be more 1.x after that but who can say, releasing is an emergent community
process)

On Thu, Jul 12, 2018 at 7:44 AM Josh Elser <[email protected]> wrote:

> I remember a passing comment, but I forget the decision: what's up for
> the 4.x release line post 4.14 and 5.0?
>
> Was 5.x going to move to master and then make 4.x branches for any more
> 4.x releases?
>
> Related question I think I know the answer to: how much longer are we
> going to continue work on the 4.x line? (as long as there are related
> HBase releases, I imagine)
>
> - Josh
>


--
Best regards,
Andrew

Words like orphans lost among the crosstalk, meaning torn from truth's
decrepit hands
   - A23, Crosstalk

Reply via email to