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

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

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

stack edited comment on HBASE-20315 at 4/30/18 11:56 PM:
---------------------------------------------------------

Example of moving an RC from dev to release:

{code}$ svn mv dev/hbase/hbase-2.0.0RC2 release/hbase/2.0.0
$ #  // Remove an old release
$ mvn rm release/hbase/2.0.0-beta-2
$ # Commit the removal and move.
$ svn commit -m "Release 2.0.0 copying 2.0.0RC2 to release. Remove 2.0.0-beta-2"
{code}

Writing the release announcement, I noticed [~busbey]'s stamping an easily finding link to our release notes up in JIRA using apache url shortener....  e.g. I used https://s.apache.org/new to create https://s.apache.org/hbase-2.0.0-JIRA-changes

I tried to push to announce but got blocked because mirrors don't have signatures and hashes. There needs to be a connection between hashes and signatures hosted on apache and the artifacts gotten from mirrors. Projects usually do this on a 'download' page. Added one with 2.0.0 as first entry over on HBASE-20510. Let me integrate into the steps filling out a row in this table...



was (Author: stack):
Example of moving an RC from dev to release:

{code}$ svn mv dev/hbase/hbase-2.0.0RC2 release/hbase/2.0.0
$ #  // Remove an old release
$ mvn rm release/hbase/2.0.0-beta-2
$ # Commit the removal and move.
$ svn commit -m "Release 2.0.0 copying 2.0.0RC2 to release. Remove 2.0.0-beta-2"
{code}

Writing the release announcement, I noticed [~busbey]'s stamping an easily finding link to our release notes up in JIRA using apache url shortener....  e.g. I used https://s.apache.org/new to create https://s.apache.org/hbase-2.0.0-JIRA-releasenotes

I tried to push to announce but got blocked because mirrors don't have signatures and hashes. There needs to be a connection between hashes and signatures hosted on apache and the artifacts gotten from mirrors. Projects usually do this on a 'download' page. Added one with 2.0.0 as first entry over on HBASE-20510. Let me integrate into the steps filling out a row in this table...


> 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: Critical
>             Fix For: 3.0.0
>
>
> 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)