[jira] [Commented] (HBASE-18767) Release hbase-2.0.0-alpha-3; Theme "Scrubbed API"
[
https://issues.apache.org/jira/browse/HBASE-18767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170219#comment-16170219
]
stack commented on HBASE-18767:
---
I need to do a clean before generating the src tgz. From [~busbey] VOTE
{code}
No good; will hold my nose for 'alpha'.
* CHANGES.txt file hasn't been updated correctly. currently has details for 0.93
* the source tarball contains binaries. this has our source tarball at
~100MiB instead of ~18MiB.
* additional ways the source tarball does not match the source tag
* * also a few dependency-reduced-pom.xml files included
* * we don't have the .pylintrc file from our source
* * also we have a spurious directory in hbase-server/src/main/site
* * we don't have hbase-native-client directory, which is in source tag
(all of the above found via recursive diff between unpacking source
tarball and checkout of tag)
{code}
> Release hbase-2.0.0-alpha-3; Theme "Scrubbed API"
> -
>
> Key: HBASE-18767
> URL: https://issues.apache.org/jira/browse/HBASE-18767
> Project: HBase
> Issue Type: Task
>Reporter: stack
> Fix For: 2.0.0-alpha-3
>
>
> From the dev mail thread: "Moving 2.0 forward", the theme is solidifying API.
> I listed a bunch of API JIRAs to address. [~mdrob] nicely tagged them all w/
> the 2.0.0-alpha-3 fix version. This issue is for pushing out alpha-3.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18767) Release hbase-2.0.0-alpha-3; Theme "Scrubbed API"
[
https://issues.apache.org/jira/browse/HBASE-18767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168321#comment-16168321
]
stack commented on HBASE-18767:
---
High-level stuff done over last day or so to generate RC (mostly out of
refguide)
{code}
735 mvn clean install -DskipTests assembly:single
-Dassembly.file=hbase-assembly/src/main/assembly/src.xml -Prelease
# Now check that can build from the src tgz And that src layout looks right.
736 cd hbase-assembly/target/
737 tar xfz hbase-2.0.0-alpha3-src.tar.gz
738 cd hbase-2.0.0-alpha3
739 mvn clean install -DskipTests assembly:single
-Dassembly.file=hbase-assembly/src/main/assembly/src.xml -Prelease
{code}
Then...
{code}
744 mvn clean install -DskipTests -Prelease
746 mvn install -DskipTests site assembly:single -Prelease
# Check tgz basically works and looks right.
747 cd hbase-assembly/target/
749 tar xfz hbase-2.0.0-alpha3-bin.tar.gz
750 ls -la hbase-2.0.0-alpha3-bin.tar.gz
751 cd hbase-2.0.0-alpha3
752 ./bin/start-hbase.sh
753 export
JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/
754 ./bin/start-hbase.sh
755 tail -f logs/hbase-stack-master-kalashnikov.att.net.log
756 ./bin/hbase org.apache.hadoop.hbase.PerformanceEvaluation
sequentialWrite 1
757 ./bin/hbase org.apache.hadoop.hbase.PerformanceEvaluation sequentiaRead 1
758 ./bin/hbase org.apache.hadoop.hbase.PerformanceEvaluation sequentialRead
1
759 vi logs/hbase-stack-master-kalashnikov.att.net.log
{code}
Tag and push to mvn
{code}
git tag -s 2.0.0-alpha-3RC0.2 -m "Second attempt at a tag on the first
2.0.0-alpha-3RC0; ignore the former in favor of this one; i.e. 2.0.0-alpha-3RC0"
770 git push --tags
771 mvn deploy -DskipTests -Papache-release -Prelease
{code}
Close repository up in mvn.
Do md5s, and sign.
{code}
629 for i in *.tar.gz; do echo $i; gpg --print-md SHA512 $i > $i.sha ; done
630 for i in *.tar.gz; do echo $i; gpg --armor --output $i.asc --detach-sig
$i ; done
631 for i in *.tar.gz; do echo $i; gpg --default-key 8ACC93D2 --armor
--output $i.asc --detach-sig $i ; done
632 gpg --verify hbase-2.0.0-alpha3-bin.tar.gz
633 gpg --verify hbase-2.0.0-alpha3-bin.tar.gz.asc
{code}
svn commit it all in a hbase-2.0.0-alpha-3RC0 dir at this location
{code}
$ svn info
Path: .
Working Copy Root Path: /Users/stack/checkouts/hbase.dev
URL: https://dist.apache.org/repos/dist/dev/hbase
Relative URL: ^/dev/hbase
Repository Root: https://dist.apache.org/repos/dist
Repository UUID: 0d268c88-bc11-4956-87df-91683dc98e59
Revision: 21246
Node Kind: directory
Schedule: normal
Last Changed Author: stack
Last Changed Rev: 21196
Last Changed Date: 2017-08-16 14:00:31 -0700 (Wed, 16 Aug 2017)
{code}
> Release hbase-2.0.0-alpha-3; Theme "Scrubbed API"
> -
>
> Key: HBASE-18767
> URL: https://issues.apache.org/jira/browse/HBASE-18767
> Project: HBase
> Issue Type: Task
>Reporter: stack
> Fix For: 2.0.0-alpha-3
>
>
> From the dev mail thread: "Moving 2.0 forward", the theme is solidifying API.
> I listed a bunch of API JIRAs to address. [~mdrob] nicely tagged them all w/
> the 2.0.0-alpha-3 fix version. This issue is for pushing out alpha-3.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18767) Release hbase-2.0.0-alpha-3; Theme "Scrubbed API"
[ https://issues.apache.org/jira/browse/HBASE-18767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168304#comment-16168304 ] stack commented on HBASE-18767: --- Pushed RC0 this morning. tgz is 180MB. Needs a diet. > Release hbase-2.0.0-alpha-3; Theme "Scrubbed API" > - > > Key: HBASE-18767 > URL: https://issues.apache.org/jira/browse/HBASE-18767 > Project: HBase > Issue Type: Task >Reporter: stack > Fix For: 2.0.0-alpha-3 > > > From the dev mail thread: "Moving 2.0 forward", the theme is solidifying API. > I listed a bunch of API JIRAs to address. [~mdrob] nicely tagged them all w/ > the 2.0.0-alpha-3 fix version. This issue is for pushing out alpha-3. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18767) Release hbase-2.0.0-alpha-3; Theme "Scrubbed API"
[ https://issues.apache.org/jira/browse/HBASE-18767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167456#comment-16167456 ] stack commented on HBASE-18767: --- Trying to put up the release but site target seems stuck in a cycle that it won't break out of it. Leaving it over night... > Release hbase-2.0.0-alpha-3; Theme "Scrubbed API" > - > > Key: HBASE-18767 > URL: https://issues.apache.org/jira/browse/HBASE-18767 > Project: HBase > Issue Type: Task >Reporter: stack > Fix For: 2.0.0-alpha-3 > > > From the dev mail thread: "Moving 2.0 forward", the theme is solidifying API. > I listed a bunch of API JIRAs to address. [~mdrob] nicely tagged them all w/ > the 2.0.0-alpha-3 fix version. This issue is for pushing out alpha-3. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18767) Release hbase-2.0.0-alpha-3; Theme "Scrubbed API"
[ https://issues.apache.org/jira/browse/HBASE-18767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167157#comment-16167157 ] stack commented on HBASE-18767: --- Running into following issue HBASE-17351 trying to build bin tar ball. Seems like we lost that fix. Did HBASE-18821 to bring it back for now. > Release hbase-2.0.0-alpha-3; Theme "Scrubbed API" > - > > Key: HBASE-18767 > URL: https://issues.apache.org/jira/browse/HBASE-18767 > Project: HBase > Issue Type: Task >Reporter: stack > Fix For: 2.0.0-alpha-3 > > > From the dev mail thread: "Moving 2.0 forward", the theme is solidifying API. > I listed a bunch of API JIRAs to address. [~mdrob] nicely tagged them all w/ > the 2.0.0-alpha-3 fix version. This issue is for pushing out alpha-3. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18767) Release hbase-2.0.0-alpha-3; Theme "Scrubbed API"
[ https://issues.apache.org/jira/browse/HBASE-18767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159690#comment-16159690 ] stack commented on HBASE-18767: --- Do this HBASE-18648 > Release hbase-2.0.0-alpha-3; Theme "Scrubbed API" > - > > Key: HBASE-18767 > URL: https://issues.apache.org/jira/browse/HBASE-18767 > Project: HBase > Issue Type: Task >Reporter: stack > Fix For: 2.0.0-alpha-3 > > > From the dev mail thread: "Moving 2.0 forward", the theme is solidifying API. > I listed a bunch of API JIRAs to address. [~mdrob] nicely tagged them all w/ > the 2.0.0-alpha-3 fix version. This issue is for pushing out alpha-3. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18767) Release hbase-2.0.0-alpha-3; Theme "Scrubbed API"
[ https://issues.apache.org/jira/browse/HBASE-18767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159426#comment-16159426 ] stack commented on HBASE-18767: --- bq. The issues which aim to "correct" our docs should be declared as Blocker. For example, incorrect link and wrong guideline. Ok. I made an umbrella issue in meantime under which we can hang 2.0.0 doc blockers. HBASE-18785 > Release hbase-2.0.0-alpha-3; Theme "Scrubbed API" > - > > Key: HBASE-18767 > URL: https://issues.apache.org/jira/browse/HBASE-18767 > Project: HBase > Issue Type: Task >Reporter: stack > Fix For: 2.0.0-alpha-3 > > > From the dev mail thread: "Moving 2.0 forward", the theme is solidifying API. > I listed a bunch of API JIRAs to address. [~mdrob] nicely tagged them all w/ > the 2.0.0-alpha-3 fix version. This issue is for pushing out alpha-3. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18767) Release hbase-2.0.0-alpha-3; Theme "Scrubbed API"
[ https://issues.apache.org/jira/browse/HBASE-18767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159418#comment-16159418 ] Chia-Ping Tsai commented on HBASE-18767: bq. Should we add a doc blocker on hbase 2? The issues which aim to "correct" our docs should be declared as Blocker. For example, incorrect link and wrong guideline. > Release hbase-2.0.0-alpha-3; Theme "Scrubbed API" > - > > Key: HBASE-18767 > URL: https://issues.apache.org/jira/browse/HBASE-18767 > Project: HBase > Issue Type: Task >Reporter: stack > Fix For: 2.0.0-alpha-3 > > > From the dev mail thread: "Moving 2.0 forward", the theme is solidifying API. > I listed a bunch of API JIRAs to address. [~mdrob] nicely tagged them all w/ > the 2.0.0-alpha-3 fix version. This issue is for pushing out alpha-3. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18767) Release hbase-2.0.0-alpha-3; Theme "Scrubbed API"
[ https://issues.apache.org/jira/browse/HBASE-18767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159380#comment-16159380 ] stack commented on HBASE-18767: --- [~chia7712] You are right. Should we add a doc blocker on hbase 2? > Release hbase-2.0.0-alpha-3; Theme "Scrubbed API" > - > > Key: HBASE-18767 > URL: https://issues.apache.org/jira/browse/HBASE-18767 > Project: HBase > Issue Type: Task >Reporter: stack > Fix For: 2.0.0-alpha-3 > > > From the dev mail thread: "Moving 2.0 forward", the theme is solidifying API. > I listed a bunch of API JIRAs to address. [~mdrob] nicely tagged them all w/ > the 2.0.0-alpha-3 fix version. This issue is for pushing out alpha-3. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18767) Release hbase-2.0.0-alpha-3; Theme "Scrubbed API"
[ https://issues.apache.org/jira/browse/HBASE-18767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159373#comment-16159373 ] Chia-Ping Tsai commented on HBASE-18767: Do we intend to revise reference guide before 2.0 release? There are 100+ issues about the docs. Personally, we will give users a negative impression of the quality if the official documents provide many of stale information... > Release hbase-2.0.0-alpha-3; Theme "Scrubbed API" > - > > Key: HBASE-18767 > URL: https://issues.apache.org/jira/browse/HBASE-18767 > Project: HBase > Issue Type: Task >Reporter: stack > Fix For: 2.0.0-alpha-3 > > > From the dev mail thread: "Moving 2.0 forward", the theme is solidifying API. > I listed a bunch of API JIRAs to address. [~mdrob] nicely tagged them all w/ > the 2.0.0-alpha-3 fix version. This issue is for pushing out alpha-3. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
