hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11730) Document release managers for non-deprecated branches
Date Thu, 18 Sep 2014 05:46:35 GMT

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

Hudson commented on HBASE-11730:
--------------------------------

FAILURE: Integrated in HBase-1.0 #195 (See [https://builds.apache.org/job/HBase-1.0/195/])
Rebased HBASE-11730 for branch-1 (mstanleyjones: rev 786418c8833fd0b9bbeb67482e3fb97c06c541fc)
* src/main/docbkx/developer.xml


> 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
>            Assignee: Misty Stanley-Jones
>             Fix For: 2.0.0, 0.99.1
>
>         Attachments: HBASE-11730.patch
>
>
> 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.3.4#6332)

Mime
View raw message