[jira] [Assigned] (HBASE-21935) Replace make_rc.sh with customized spark/dev/create-release

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

     [ https://issues.apache.org/jira/browse/HBASE-21935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack reassigned HBASE-21935:
-----------------------------

        Assignee: stack
          Labels: rm  (was: )
    Release Note: 
These scripts came originally from spark [1]. They were then modified to suit hbase context. Supercedes the old ../make_rc.sh script because what is here is more comprehensive doing more steps of the RM process as well as running in a container so the RM build environment can be a constant.

 It:
     * Tags release
     * Sets version to the release version
     * Sets version to next SNAPSHOT version.
     * Builds, signs, and hashes all artifacts.
     * Pushes release tgzs to the dev dir in a apache dist.
     * Pushes to repository.apache.org staging.

 The entry point is the do-release-docker.sh script. Pass -h to see available options. For example, running below will do all steps above using the 'rm' dir under Downloads as workspace:

     $ ./do-release-docker.sh  -d ~/Downloads/rm

1. https://github.com/apache/spark/tree/master/dev/create-release

TODO: Practice some releases w/ these scripts. I just put up a 2.0.5RC0. Seemed to work fine.
TODO: Doc. Revive the RM section of refguide to use this script instead. See if can use any of this spark doc in ours: https://spark.apache.org/release-process.html
TODO: Auto-generate the release notes and changes list. Should be possible.
TODO: Auto-generate the API diff file.
TODO: Add check that all issues resolved in JIRA before starting?

> Replace make_rc.sh with customized spark/dev/create-release
> -----------------------------------------------------------
>
>                 Key: HBASE-21935
>                 URL: https://issues.apache.org/jira/browse/HBASE-21935
>             Project: HBase
>          Issue Type: Task
>          Components: rm
>            Reporter: stack
>            Assignee: stack
>            Priority: Minor
>              Labels: rm
>         Attachments: HBASE-21935.branch-2.1.001.patch
>
>
> The spark/dev/create-release is more comprehensive than our hokey make_rc.sh script. It codifies the bulk of the RM process from tagging, version-setting, building, signing, and pushing. It does it in a container so environment is same each time. It has a bunch of spark-specifics as is -- naturally -- but should be possible to pull it around to suit hbase RM'ing. It'd save a bunch of time and would allow us to get to a place where RM'ing is canned, evolvable, and consistent.
> I've been hacking on the tooling before the filing of this JIRA and was polluting branch-2.0 w/ tagging and reverts. Let me make a branch named for this JIRA to play with (There is a dry-run flag but it too needs work...).



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