hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19152) Update refguide 'how to build an RC' and the make_rc.sh script
Date Wed, 01 Nov 2017 22:19:00 GMT

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

stack commented on HBASE-19152:

Dunno. Looks like old knowledge. Probably from before this time when it looks like it was
added (when it was probably just recast from elsewhere)

tree 23345eae23ca7b51f11c451ccbe8ef49f641e5c1
parent 95f1fe52ed486fea21587739af7a18583d667b31
author Nick Dimiduk <ndimiduk@apache.org> Mon May 11 14:43:58 2015 -0700
committer Nick Dimiduk <ndimiduk@apache.org> Mon May 11 15:26:41 2015 -0700

HBASE-13665 Fix docs and site building on branch-1

make_rc.sh has both on the command-line.  

Up here in https://repo.maven.apache.org/maven2/org/apache/apache/18/apache-18.pom it calls
it the 'release-profile'

In maven super pom, there is a release-profile Profile.

Trying w/ apache-release only.

> Update refguide 'how to build an RC' and the make_rc.sh script
> --------------------------------------------------------------
>                 Key: HBASE-19152
>                 URL: https://issues.apache.org/jira/browse/HBASE-19152
>             Project: HBase
>          Issue Type: Sub-task
>          Components: build
>            Reporter: stack
>            Assignee: stack
>             Fix For: 2.0.0-beta-1
>         Attachments: 0001-HBASE-19152-Update-refguide-how-to-build-an-RC-and-t.patch,
HBASE-19152.master.001.patch, HBASE-19152.master.002.patch, HBASE-19152.master.003.patch,
> Update the section on how to build an RC. In particular, note that tags should be signed
and talk up the new way of building the src tgz (after a Sean suggestion) including removal
of old means src.xml from hbase-assembly. Update the make_rc.sh script so it works for branch-2

This message was sent by Atlassian JIRA

View raw message