hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ishan Chhabra (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11642) EOL 0.96
Date Tue, 05 Aug 2014 08:27:12 GMT

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

Ishan Chhabra commented on HBASE-11642:
---------------------------------------

Hmm, I agree and can relate to the pain associated with a co-ordinated upgrade having gone
through it myself. 

Thinking about it more, I agree a full EOL is not a good idea for 0.94, but is there are way
to make its status more clearer and explicit (maybe "extended maintenance" like python 2.x)
so that people running smaller clusters would consider upgrades and newer users don't use
0.94 accidentally (I see some of them doing that mostly because they start with CDH 4). It
is easy for a casual observer to think that 0.94 is having active releases, whereas it is
made clear in the JIRAs that new features should not be added to this branch. 

As a side note, this line should be definitely fixed in the download pages (eg. http://www.carfab.com/apachesoftware/hbase/)

"The 0.96.x series supercedes 0.94.x. We are leaving the 'stable' pointer on the latest 0.94.x
for now while 0.96 is still 'fresh'."


> 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)

Mime
View raw message