[ 
https://issues.apache.org/jira/browse/HBASE-11642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14085866#comment-14085866
 ] 

Lars Hofhansl commented on HBASE-11642:
---------------------------------------

[~ishanc] In the end this an open source project. As long as there is a 
maintainer there'll be updates. :)

The reasoning for retiring 0.96 is that everyone should rather go to 0.98 (you 
can do a rolling upgrade from 0.96 to 0.98, no data upgrade required).
If we had semantic versioning going from 0.96 to 0.98 would something like 
going from version 2.0.x to 2.1.x (i.e. a minor version update). We're just 
saying: No more patches for the 2.0 code line, please upgrade to 2.1.x for 
bugfixes.

0.94 is the prior major version. Retiring that in favor of 0.98 would be like 
going from 1.0.x to 2.x.y, with no rolling upgrades, no client-server protocol 
compatibility, and a data upgrade step and new version of Hadoop (likely) 
required.

So we'd be maintaining the equivalent of 1.x.y, and 2.x.y.

Eventually 0.94 will be retired (i.e. nobody will contribute patches to it any 
more). If we want save the work maintaining 0.94 or nobody is using it anymore 
anyway we can retire it soon. If we want to keep maintaining it for folks who 
cannot risk upgrading their data we can do so too.

Why are you asking? You feel we should retire 0.94 as well? Or you're worried 
we might retire it?


> EOL 0.96
> --------
>
>                 Key: HBASE-11642
>                 URL: https://issues.apache.org/jira/browse/HBASE-11642
>             Project: HBase
>          Issue Type: Task
>            Reporter: stack
>            Assignee: stack
>
> Do the work to EOL 0.96.
> + No more patches on 0.96
> + Remove 0.96 from downloads.
> + If user has issue with 0.96 and needs fix, fix it in 0.98 and have the user 
> upgrade to get the fix.
> + Write email to user list stating 0.96 has been EOL'd September 1st? And add 
> notice to refguide.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to