[
https://issues.apache.org/jira/browse/HBASE-21935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16789847#comment-16789847
]
Sean Busbey commented on HBASE-21935:
-------------------------------------
thanks for the heads up. got the correct one, I think.
{code}
Busbey-MBA:hbase busbey$ smart-apply-patch --project=hbase --committer
HBASE-21935
Processing: HBASE-21935
WARNING: HBASE-21935 issue status is not matched with "Patch Available".
HBASE-21935 patch is being downloaded at Mon Mar 11 13:21:50 CDT 2019 from
https://issues.apache.org/jira/secure/attachment/12962016/HBASE-21935.branch-2.0.005.patch
-> Downloaded
Applying the patch:
Mon Mar 11 13:21:51 CDT 2019
cd /Users/busbey/tmp_projects/hbase
git am --signoff --whitespace=fix -p1 /tmp/yetus-758.11257/patch
.git/rebase-apply/patch:770: new blank line at EOF.
+
warning: 1 line adds whitespace errors.
Applying: HBASE-21935 Replace make_rc.sh with customized
spark/dev/create-release
{code}
> 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.0.001.patch,
> HBASE-21935.branch-2.0.002.patch, HBASE-21935.branch-2.0.003.patch,
> HBASE-21935.branch-2.0.004.patch, HBASE-21935.branch-2.0.005.patch,
> HBASE-21935.branch-2.1.001.patch, HBASE-21935.branch-2.1.002.patch,
> HBASE-21935.branch-2.1.003.patch, HBASE-21935.branch-2.1.004.patch,
> HBASE-21935.branch-2.1.005.patch, HBASE-21935.branch-2.1.006.patch,
> HBASE-21935.branch-2.1.007.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)
