hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11730) Document release managers for non-deprecated branches
Date Wed, 10 Sep 2014 15:36:36 GMT

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

Sean Busbey commented on HBASE-11730:

Could we just leave out EOL'd versions? Seems like if an issue is severe enough to warrant
resurrecting one of them, it's going to require a dev@hbase email anyways.

That would remove the entries for 0.96 and < 0.94.

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

View raw message