[jira] [Comment Edited] (HBASE-23120) Fix ref guide - Release process

["Sakthi (Jira)" <ji...@apache.org>]

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

Sakthi edited comment on HBASE-23120 at 2/28/20 11:33 PM:
----------------------------------------------------------

Is missing the steps to do after the voting succeeds:

* Push rel/release-version at the commit where the passing RC is tagged at
* Publish the nexus repo - (click the 'Release' button to release the artifacts to central. The release process will automatically drop and delete the staging repository)
* Move the RC from the dev directory to the releases directory (NOTE: the date this action is performed, is considered to be the date of release.)
* Enter the date of release at reporter.a.o (https://issues.apache.org/jira/browse/HBASE-23012?focusedCommentId=16958944&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16958944)
* Update the Downloads page with link and date of the release
* Move the version of the branch to next SNAPSHOT version or consider EOL by starting up a discussion in private/dev
* Enter the release date in CHANGES.txt
* Mark the JIRA version released


was (Author: jatsakthi):
Is missing the steps to do after the voting succeeds:

* Push rel/release-version at the commit where the passing RC is tagged at
* Publish the nexus repo - (click the 'Release' button to release the artifacts to central. The release process will automatically drop and delete the staging repository)
* Move the RC from the dev directory to the releases directory (NOTE: the date this action is performed, is considered to be the date of release.)
* Enter the date of release at reporter.a.o
* Update the Downloads page with link and date of the release
* Move the version of the branch to next SNAPSHOT version or consider EOL by starting up a discussion in private/dev
* Enter the release date in CHANGES.txt
* Mark the JIRA version released

> Fix ref guide - Release process
> -------------------------------
>
>                 Key: HBASE-23120
>                 URL: https://issues.apache.org/jira/browse/HBASE-23120
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Sakthi
>            Assignee: Sakthi
>            Priority: Minor
>             Fix For: 3.0.0
>
>
> The example is of a sample ~/.m2/settings.xml file.
> {code:java}
> <!- To publish a snapshot of some part of Maven -->
> {code}
>  is not a proper comment. 
> Also I think here,
> {code:java}
> <!--Keyname is something like this ... 00A5F21E... do gpg --list-keys to find it-->
> {code}
> the double hyphened --list-keys shouldn't be used. It leads to FATAL error like the one below: 
> {code:java}
> [FATAL] Non-parseable settings
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)