[
https://issues.apache.org/jira/browse/HBASE-11730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097011#comment-14097011
]
Sean Busbey commented on HBASE-11730:
-------------------------------------
At a minimum, I think having a "ask Foo about inclusion in release X" would be
useful, in the same way we have an [explanation for and pointers to the
component owners|http://hbase.apache.org/book.html#community.roles]. It gives
new people a leg up on figuring out the existing social norm instead of
requiring them to reverse engineer it from "ping Foo for branch X" notes in
jira.
Actually maybe this should be under the community roles section and not in
codelines as I suggested earlier.
> 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)
