[jira] [Commented] (HBASE-11730) Document release managers for non-deprecated branches

["Sean Busbey (JIRA)" <ji...@apache.org>]

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

Sean Busbey commented on HBASE-11730:
-------------------------------------

>From watching Jira and talking to [~jmhsieh], the current RM list is:

* < 0.94: [~stack]
* 0.94: [~lhofhansl]
* 0.96: [~stack] (eol or soon to be)
* 0.98: [~apurtell]
* 1.0: [~enis]

> Document release managers for non-deprecated branches
> -----------------------------------------------------
>
>                 Key: HBASE-11730
>                 URL: https://issues.apache.org/jira/browse/HBASE-11730
>             Project: HBase
>          Issue Type: Task
>          Components: documentation
>            Reporter: Sean Busbey
>
> New development goes against trunk and is backported as desired to existing release branches. From what I have seen on the jira, it looks like each branch's release manager makes the call on backporting a particular issue.
> We should document both this norm and who the relevant release manager is for each branch.
> In the current docs, I'd suggest adding the RM list to the "Codelines" section (18.11.1) and add a brief explanation of pinging the RM as a new section after "submitting a patch again" (18.12.6).
> Post HBASE-4593, the note about pinging a prior branch RM should just go as a bullet in the "patch workflow."



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