[jira] [Comment Edited] (HBASE-20315) Document post release process steps for RM

["Andrew Purtell (JIRA)" <ji...@apache.org>]

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

Andrew Purtell edited comment on HBASE-20315 at 3/29/18 5:05 PM:
-----------------------------------------------------------------

Something like
 # Close the vote.
 # If your code signing key is not in the project KEYS file, ask a PMC member to add it for you. (Update to KEYS file in dist/release/ requires PMC karma.)
 # Move the RC binaries to release. The move to dist/release/ requires PMC karma, so please ask a PMC member to execute this command for you if you don't have it. If there are any other staged RC binaries in dev/hbase/ for earlier/failed RCs, remove them. For example, this was done to release 1.4.2: {{svn mv -m"Release HBase 1.4.2" [https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.2RC0] [https://dist.apache.org/repos/dist/release/hbase/1.4.2}}
 # Ensure the release state for the version is set to Released in JIRA. If you are unable to do this, you will need a PMC member to make a one time change to your permissions on the project.
 # Update release metadata in reporter.apache.org. Go to [https://reporter.apache.org/#releases_hbase] . Click on "Fetch releases from JIRA". If you are not a member of the PMC, you will need to ask a PMC member to do this for you.
 # Log on to repository.apache.org, go to the staging repository you made for the RC that passed, click 'Release'. If there are any other staging repositories for earlier/failed RCs, go to each of them and click 'Drop'.
 # Wait 24 hours for propagation to mirrors.
 # Send release announcement.

 




was (Author: apurtell):
Something like
 # Close the vote.
 # If your code signing key is not in the project KEYS file, ask a PMC member to add it for you. (Update to KEYS file in dist/release/ requires PMC karma.)
 # Move the RC binaries to release. The move to dist/release/ requires PMC karma, so please ask a PMC member to execute this command for you if you don't have it. If there are any other staged RC binaries in dev/hbase/ for earlier/failed RCs, remove them. For example, this was done to release 1.4.2:


svn mv -m"Release HBase 1.4.2" [https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.2RC0] [https://dist.apache.org/repos/dist/release/hbase/1.4.2
]
 # Ensure the release state for the version is set to Released in JIRA. If you are unable to do this, you will need a PMC member to make a one time change to your permissions on the project.
 # Update release metadata in reporter.apache.org. Go to [https://reporter.apache.org/#releases_hbase] . Click on "Fetch releases from JIRA". If you are not a member of the PMC, you will need to ask a PMC member to do this for you.
 # Log on to repository.apache.org, go to the staging repository you made for the RC that passed, click 'Release'. If there are any other staging repositories for earlier/failed RCs, go to each of them and click 'Drop'.
 # Wait 24 hours for propagation to mirrors.
 # Send release announcement.

> Document post release process steps for RM
> ------------------------------------------
>
>                 Key: HBASE-20315
>                 URL: https://issues.apache.org/jira/browse/HBASE-20315
>             Project: HBase
>          Issue Type: Task
>          Components: build, documentation
>            Reporter: Andrew Purtell
>            Priority: Major
>
> We should document post release steps that RMs have to take and add it to the 'How To Release' section of the refguide.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)