[
https://issues.apache.org/jira/browse/HBASE-19583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16303404#comment-16303404
]
Sean Busbey commented on HBASE-19583:
-------------------------------------
back in HBASE-16215 [~enis] requested we not delete previous release lines.
there's discussion there that's worth reading.
Speaking as a RM, I'd rather we not list RMs for non-maintained branches.
There's already recognition via the archived VOTEs and ANNOUNCE emails. Since
the RM list is used for folks to figure out who to ask for something (namely
"include X in release Y" or "hey remember we need another release on line Y"),
having a list of prior RMs seems to me likely to encourage folks to reach out
for help after the RM in question has already made clear they've finished their
part in that release line.
> Delete EOL branches - branch-1.0 and branch-1.1
> -----------------------------------------------
>
> Key: HBASE-19583
> URL: https://issues.apache.org/jira/browse/HBASE-19583
> Project: HBase
> Issue Type: Bug
> Reporter: Appy
> Priority: Minor
>
> wdys [~enis] [~ndimiduk]?
> This needs updating too - http://hbase.apache.org/book.html#_release_managers.
> I think we should mention RMs for all branches, even eols, if only in other
> table. Good way to recognize past efforts.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
