Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 14 Aug 2014 18:08:12 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12733790.1407942735374.84342.1408039692497@arcas>
In-Reply-To: <JIRA.12733790.1407942735374@arcas>
References: <JIRA.12733790.1407942735374@arcas>
Subject: [jira] [Commented] (HBASE-11730) Document release managers for
 non-deprecated branches
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew Purtell commented on HBASE-11730:
----------------------------------------

bq.  I think having a "ask Foo about inclusion in release X" would be useful

That sounds reasonable to me

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