[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[
https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16429619#comment-16429619
]
Hudson commented on HBASE-18828:
Results for branch branch-2.0
[build #143 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/143/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/140//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/143//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/143//JDK8_Nightly_Build_Report_(Hadoop3)/]
> [2.0] Generate CHANGES.txt
> --
>
> Key: HBASE-18828
> URL: https://issues.apache.org/jira/browse/HBASE-18828
> Project: HBase
> Issue Type: Sub-task
>Reporter: stack
>Assignee: stack
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-18828.branch-2.0.001.patch,
> HBASE-18828.branch-2.0.002.patch, HBASE-18828.branch-2.0.003.patch,
> changelog.md, hbase_branches.svg, releasenotes.md
>
>
> See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it
> into refguide while at it..)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[
https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16429507#comment-16429507
]
stack commented on HBASE-18828:
---
Pushed ANOTHER addendum that fixes the comment. I was pointing at wrong JIRA
ID.
{code}
commit 4ffdca6f2b441d9de3b28531760b19b48ed7 (HEAD -> 2.0xx,
origin/branch-2.0)
Author: Michael Stack
Date: Sat Apr 7 11:32:47 2018 -0700
HBASE-18828 [2.0] Generate CHANGES.txt; ADDENDUM2 Fix which JIRA we refer
to in comment
diff --git a/CHANGES.md b/CHANGES.md
index 62af42678d..5c7f90f936 100644
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -21,12 +21,12 @@
CHANGES.md and RELEASENOTES.md were generated using yetus releasedocmaker.
First make sure what is in JIRA agrees with what is in git and vice-versa
-(See HBASE-14175 for original exposition on how to do this followed by
+(See HBASE-14025 for original exposition on how to do this followed by
the travails of various release managers. See also HBASE-18828 for a
deriviative makes the move to yetus releasedocmaker).
Then make sure that anything in current release as noted in JIRA has
-not made it out in earlier major/minor (see HBASE-14175 for how to
+not made it out in earlier major/minor (see HBASE-14025 for how to
reconcile which).
Obtain a yetus release (see HBASE-18828 for some help). To run
diff --git a/RELEASENOTES.md b/RELEASENOTES.md
index 6b11c63a87..41240ce1b4 100644
--- a/RELEASENOTES.md
+++ b/RELEASENOTES.md
@@ -22,12 +22,12 @@
CHANGES.md and RELEASENOTES.md were generated using yetus releasedocmaker.
First make sure what is in JIRA agrees with what is in git and vice-versa
-(See HBASE-14175 for original exposition on how to do this followed by
+(See HBASE-14025 for original exposition on how to do this followed by
the travails of various release managers. See also HBASE-18828 for a
deriviative makes the move to yetus releasedocmaker).
Then make sure that anything in current release as noted in JIRA has
-not made it out in earlier major/minor (see HBASE-14175 for how to
+not made it out in earlier major/minor (see HBASE-14025 for how to
reconcile which).
Obtain a yetus release (see HBASE-18828 for some help). To run
{code}
> [2.0] Generate CHANGES.txt
> --
>
> Key: HBASE-18828
> URL: https://issues.apache.org/jira/browse/HBASE-18828
> Project: HBase
> Issue Type: Sub-task
>Reporter: stack
>Assignee: stack
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-18828.branch-2.0.001.patch,
> HBASE-18828.branch-2.0.002.patch, HBASE-18828.branch-2.0.003.patch,
> changelog.md, hbase_branches.svg, releasenotes.md
>
>
> See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it
> into refguide while at it..)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[
https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16429466#comment-16429466
]
stack commented on HBASE-18828:
---
Ok. Pushed .003 to branch-2.0. I then pushed an addendum that adds a comment to
head of the two new files that talks up how they were generated pointing back
to HBASE-14175 and to here:
{code}
+CHANGES.md and RELEASENOTES.md were generated using yetus releasedocmaker.
+
+First make sure what is in JIRA agrees with what is in git and vice-versa
+(See HBASE-14175 for original exposition on how to do this followed by
+the travails of various release managers. See also HBASE-18828 for a
+deriviative makes the move to yetus releasedocmaker).
+
+Then make sure that anything in current release as noted in JIRA has
+not made it out in earlier major/minor (see HBASE-14175 for how to
+reconcile which).
+
+Obtain a yetus release (see HBASE-18828 for some help). To run
+releasedocmaker, do as follows (below example is for hbase-2.0.0):
+
+ $ ./release-doc-maker/releasedocmaker.py -p HBASE --fileversions \
+-v 2.0.0 -l --sortorder=newer --skip-credits
+
+Rename the output as CHANGES.md and RELEASENOTES.md. Edit both to put
+document title above the apache license so markdown readers work. You
+may have to bulk import old-style CHANGES.txt on to the end in a code
+comment to preserve continuity of the CHANGELOG.
{code}
So, the CHANGES are current as of now. They will rot before I make the RC but
it will just be a case of re-running the tool and some hackery... small
potatoes. Let resolve this then as done and just add a note on releasing 2.0.0
to make sure I do the regeneration. The hard work is done in here (the
resolving git and JIRA records).
> [2.0] Generate CHANGES.txt
> --
>
> Key: HBASE-18828
> URL: https://issues.apache.org/jira/browse/HBASE-18828
> Project: HBase
> Issue Type: Sub-task
>Reporter: stack
>Assignee: stack
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-18828.branch-2.0.001.patch,
> HBASE-18828.branch-2.0.002.patch, HBASE-18828.branch-2.0.003.patch,
> changelog.md, hbase_branches.svg, releasenotes.md
>
>
> See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it
> into refguide while at it..)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[
https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16429220#comment-16429220
]
Hadoop QA commented on HBASE-18828:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
20s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} branch-2.0 Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
11s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
9s{color} | {color:green} branch-2.0 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 15m
49s{color} | {color:green} branch-2.0 passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 22m
39s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
20s{color} | {color:green} branch-2.0 passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
11s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
7s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 15m
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 15m
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
2s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 3m
39s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
13m 24s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.5 2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
20s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green}188m
19s{color} | {color:green} root in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
47s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}249m 4s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:369877d |
| JIRA Issue | HBASE-18828 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12917919/HBASE-18828.branch-2.0.003.patch
|
| Optional Tests | asflicense javac javadoc unit xml shadedjars
hadoopcheck compile |
| uname | Linux f75000a968b3 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11
12:16:42 UTC 2017 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | branch-2.0 / bdd87945e7 |
| maven | version: Apache Maven 3.5.3
(3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z) |
| Default Java | 1.8.0_162 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/12333/testReport/ |
| Max. process+thread count | 4760 (vs. ulimit of 1) |
| modules | C: hbase-assembly . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/12333/console |
| Powered by | Apache Yetus 0.7.0 http://yetus.apache.org |
This message was automatically generated.
> [2.0] Generate CHANGES.txt
> --
>
> Key: HBASE-18828
> URL: https://issues.apache.org/jira/browse/HBASE-18828
>
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[
https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16429147#comment-16429147
]
Hadoop QA commented on HBASE-18828:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
20s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} branch-2.0 Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 1m
9s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 6m
39s{color} | {color:green} branch-2.0 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 22m
26s{color} | {color:green} branch-2.0 passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 35m
35s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 4m
12s{color} | {color:green} branch-2.0 passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
19s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
40s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 22m
39s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 22m
39s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
0s{color} | {color:red} The patch has 178 line(s) that end in whitespace. Use
git apply --whitespace=fix <>. Refer
https://git-scm.com/docs/git-apply {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
8s{color} | {color:red} The patch 10 line(s) with tabs. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
4s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m
16s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
19m 29s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.5 2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 3m
56s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green}166m
10s{color} | {color:green} root in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
47s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}258m 46s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:369877d |
| JIRA Issue | HBASE-18828 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12917894/HBASE-18828.branch-2.0.002.patch
|
| Optional Tests | asflicense javac javadoc unit xml shadedjars
hadoopcheck compile |
| uname | Linux ca6138b055b1 3.13.0-139-generic #188-Ubuntu SMP Tue Jan 9
14:43:09 UTC 2018 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build@2/component/dev-support/hbase-personality.sh
|
| git revision | branch-2.0 / 5bf3b33a57 |
| maven | version: Apache Maven 3.5.3
(3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z) |
| Default Java | 1.8.0_162 |
| whitespace |
https://builds.apache.org/job/PreCommit-HBASE-Build/12327/artifact/patchprocess/whitespace-eol.txt
|
| whitespace |
https://builds.apache.org/job/PreCommit-HBASE-Build/12327/artifact/patchprocess/whitespace-tabs.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/12327/testReport/ |
| Max.
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[ https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16429128#comment-16429128 ] stack commented on HBASE-18828: --- .003 changes the pom... will commit so 'the people' can acclimatize to new formats. Thanks [~busbey] > [2.0] Generate CHANGES.txt > -- > > Key: HBASE-18828 > URL: https://issues.apache.org/jira/browse/HBASE-18828 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > Attachments: HBASE-18828.branch-2.0.001.patch, > HBASE-18828.branch-2.0.002.patch, HBASE-18828.branch-2.0.003.patch, > changelog.md, hbase_branches.svg, releasenotes.md > > > See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it > into refguide while at it..) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[
https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16429114#comment-16429114
]
Hadoop QA commented on HBASE-18828:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
13s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} branch-2.0 Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
16s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
21s{color} | {color:green} branch-2.0 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 15m
9s{color} | {color:green} branch-2.0 passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 22m
12s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
12s{color} | {color:green} branch-2.0 passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
9s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
6s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 15m
20s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 15m
20s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
0s{color} | {color:red} The patch has 178 line(s) that end in whitespace. Use
git apply --whitespace=fix <>. Refer
https://git-scm.com/docs/git-apply {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
2s{color} | {color:red} The patch 10 line(s) with tabs. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
2s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 3m
28s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
13m 4s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.5 2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
22s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green}142m
5s{color} | {color:green} root in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
49s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}201m 55s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:369877d |
| JIRA Issue | HBASE-18828 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12917894/HBASE-18828.branch-2.0.002.patch
|
| Optional Tests | asflicense javac javadoc unit xml shadedjars
hadoopcheck compile |
| uname | Linux 63a8af8ecafc 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12
13:48:03 UTC 2016 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | branch-2.0 / 5bf3b33a57 |
| maven | version: Apache Maven 3.5.3
(3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z) |
| Default Java | 1.8.0_162 |
| whitespace |
https://builds.apache.org/job/PreCommit-HBASE-Build/12328/artifact/patchprocess/whitespace-eol.txt
|
| whitespace |
https://builds.apache.org/job/PreCommit-HBASE-Build/12328/artifact/patchprocess/whitespace-tabs.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/12328/testReport/ |
| Max. pro
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[ https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16429064#comment-16429064 ] Sean Busbey commented on HBASE-18828: - no that's it. not sure why i didn't see it before. > [2.0] Generate CHANGES.txt > -- > > Key: HBASE-18828 > URL: https://issues.apache.org/jira/browse/HBASE-18828 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > Attachments: HBASE-18828.branch-2.0.001.patch, > HBASE-18828.branch-2.0.002.patch, changelog.md, hbase_branches.svg, > releasenotes.md > > > See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it > into refguide while at it..) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[ https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428891#comment-16428891 ] stack commented on HBASE-18828: --- bq. Does RAT not recognize the header? It looks like it does been make_rc'ing here locally. Let me undo above. bq. v2's commit message needs to include a jira ID It has one, no? commit 561bd28440d5e17303a2104280512960a28862ac (HEAD) Author: Michael Stack Date: Fri Apr 6 11:43:20 2018 -0700 HBASE-18828 [2.0] Generate CHANGES.txt ... Maybe you mean something else? > [2.0] Generate CHANGES.txt > -- > > Key: HBASE-18828 > URL: https://issues.apache.org/jira/browse/HBASE-18828 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > Attachments: HBASE-18828.branch-2.0.001.patch, > HBASE-18828.branch-2.0.002.patch, changelog.md, hbase_branches.svg, > releasenotes.md > > > See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it > into refguide while at it..) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[
https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428872#comment-16428872
]
Sean Busbey commented on HBASE-18828:
-
{code}
diff --git a/pom.xml b/pom.xml
833**/CHANGES.txt
834+ **/CHANGES.md
835+ **/RELEASENOTES.md
{code}
Does RAT not recognize the header?
> [2.0] Generate CHANGES.txt
> --
>
> Key: HBASE-18828
> URL: https://issues.apache.org/jira/browse/HBASE-18828
> Project: HBase
> Issue Type: Sub-task
>Reporter: stack
>Assignee: stack
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-18828.branch-2.0.001.patch,
> HBASE-18828.branch-2.0.002.patch, changelog.md, hbase_branches.svg,
> releasenotes.md
>
>
> See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it
> into refguide while at it..)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[ https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428867#comment-16428867 ] Sean Busbey commented on HBASE-18828: - v2's commit message needs to include a jira ID > [2.0] Generate CHANGES.txt > -- > > Key: HBASE-18828 > URL: https://issues.apache.org/jira/browse/HBASE-18828 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > Attachments: HBASE-18828.branch-2.0.001.patch, > HBASE-18828.branch-2.0.002.patch, changelog.md, hbase_branches.svg, > releasenotes.md > > > See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it > into refguide while at it..) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[ https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428832#comment-16428832 ] stack commented on HBASE-18828: --- Thanks. .002 updates components.xml, poms and docs to reference the .md file instead (and to include the new RELEASENOTES.md file). > [2.0] Generate CHANGES.txt > -- > > Key: HBASE-18828 > URL: https://issues.apache.org/jira/browse/HBASE-18828 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > Attachments: HBASE-18828.branch-2.0.001.patch, > HBASE-18828.branch-2.0.002.patch, changelog.md, hbase_branches.svg, > releasenotes.md > > > See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it > into refguide while at it..) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[
https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428781#comment-16428781
]
Sean Busbey commented on HBASE-18828:
-
the assembly refers to CHANGES.txt for making our binary artifact over in
{{hbase-assembly/src/main/assembly/components.xml}}
> [2.0] Generate CHANGES.txt
> --
>
> Key: HBASE-18828
> URL: https://issues.apache.org/jira/browse/HBASE-18828
> Project: HBase
> Issue Type: Sub-task
>Reporter: stack
>Assignee: stack
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-18828.branch-2.0.001.patch, changelog.md,
> hbase_branches.svg, releasenotes.md
>
>
> See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it
> into refguide while at it..)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[ https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428774#comment-16428774 ] stack commented on HBASE-18828: --- .001 Removed CHANGES.txt. Replaced with CHANGES.md. Added RELEASENOTES.md. > [2.0] Generate CHANGES.txt > -- > > Key: HBASE-18828 > URL: https://issues.apache.org/jira/browse/HBASE-18828 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > Attachments: HBASE-18828.branch-2.0.001.patch, changelog.md, > hbase_branches.svg, releasenotes.md > > > See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it > into refguide while at it..) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[
https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428755#comment-16428755
]
stack commented on HBASE-18828:
---
Generated release notes and changes doing below
{code} ./release-doc-maker/releasedocmaker.py -p HBASE --fileversions -v 2.0.0
-l --sortorder=newer --skip-credits{code}
Be warned that the apache license up top breaks my markdown viewer at least...
I then did bulk import of the hbase 1.0.0 release notes (which only over 0.99.0
=> 1.0.0).
Let me put up a patch.
> [2.0] Generate CHANGES.txt
> --
>
> Key: HBASE-18828
> URL: https://issues.apache.org/jira/browse/HBASE-18828
> Project: HBase
> Issue Type: Sub-task
>Reporter: stack
>Assignee: stack
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: changelog.md, hbase_branches.svg, releasenotes.md
>
>
> See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it
> into refguide while at it..)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[ https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428668#comment-16428668 ] stack commented on HBASE-18828: --- bq. "sometimes stuff mistakenly still claims your release because it went to both post-branching" Indeed. Ok. Running bulk JIRA edit to remove 2.0.0 from all JIRAs that made it out between merge-base and 1.0.0; i.e. releases 0.99.0 => 1.0.0. > [2.0] Generate CHANGES.txt > -- > > Key: HBASE-18828 > URL: https://issues.apache.org/jira/browse/HBASE-18828 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > Attachments: changelog.md, hbase_branches.svg, releasenotes.md > > > See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it > into refguide while at it..) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[ https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428660#comment-16428660 ] Sean Busbey commented on HBASE-18828: - Just saw your updated comment. :) I'd say yes, we should remove stuff that made it into 0.99 -> 1.0.0. I thought the old recipe for "verify jira reflects git" included that as a step for "sometimes stuff mistakenly still claims your release because it went to both post-branching" > [2.0] Generate CHANGES.txt > -- > > Key: HBASE-18828 > URL: https://issues.apache.org/jira/browse/HBASE-18828 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > Attachments: changelog.md, hbase_branches.svg, releasenotes.md > > > See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it > into refguide while at it..) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[
https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428659#comment-16428659
]
Sean Busbey commented on HBASE-18828:
-
bq. What command you running?
{{git hist origin/branch-2.0 origin/master rel/1.0.0 > some_file.txt}}
then editing some_file.txt to make the elided bits w/counts.
{{git hist}} is an alias I have local:
{code}
hist = log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s
%Cgreen(%cr)%Creset' --abbrev-commit --date=relative
{code}
{quote}
Currently I'm thinking I need to figure what is in hbase1 that is also in
hbase2 and remove 2.0.0 from JIRA for those commits. You suggesting otherwise?
{quote}
you mean like remove things that landed in any branch-1 release? or just the
stuff from the 1.0.0 related release?
> [2.0] Generate CHANGES.txt
> --
>
> Key: HBASE-18828
> URL: https://issues.apache.org/jira/browse/HBASE-18828
> Project: HBase
> Issue Type: Sub-task
>Reporter: stack
>Assignee: stack
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: changelog.md, hbase_branches.svg, releasenotes.md
>
>
> See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it
> into refguide while at it..)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[ https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428608#comment-16428608 ] stack commented on HBASE-18828: --- Yeah, seems like simple JIRA edit. Remove 2.0.0 as fixVersion on any issue that was in 0.99.0=>1.0.0 (svg at least did me the service or reminding of our 0.99.x lineage). Waiting on [~busbey] ok in case has better idea. Thanks. > [2.0] Generate CHANGES.txt > -- > > Key: HBASE-18828 > URL: https://issues.apache.org/jira/browse/HBASE-18828 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > Attachments: changelog.md, hbase_branches.svg, releasenotes.md > > > See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it > into refguide while at it..) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[ https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428573#comment-16428573 ] stack commented on HBASE-18828: --- Thanks for the help. I made the graph last night, was impressed by the spaghetti then went to bed saving pleasure of deciphering for this morning. You view saved me some head-scratching. Thanks. bq. would be better to use master instead of branch-2 I think What command you running? Currently I'm thinking I need to figure what is in hbase1 that is also in hbase2 and remove 2.0.0 from JIRA for those commits. You suggesting otherwise? > [2.0] Generate CHANGES.txt > -- > > Key: HBASE-18828 > URL: https://issues.apache.org/jira/browse/HBASE-18828 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > Attachments: changelog.md, hbase_branches.svg, releasenotes.md > > > See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it > into refguide while at it..) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[
https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428547#comment-16428547
]
Sean Busbey commented on HBASE-18828:
-
How's this as a start?
{code}
* 369877d07a - (HEAD -> branch-2.0, origin/branch-2.0) HBASE-20308 Dockerfile
for test must include git. (9 days ago)
* 2e612527aa - HBASE-20130 (ADDENDUM) Use defaults (16020 & 16030) as base
ports when the RS is bound to localhost (10 days ago)
* 24f19fd5f0 - HBASE-20199 Add a unit test to verify flush and snapshot
permission requirements aren't excessive (10 days ago)
* 163c8beeba - HBASE-20280 Fix possibility of deadlocking in
refreshFileConnections (10 days ago)
... 59 commits
* dc845a7df9 - HBASE-20075 remove logic for branch-1.1 nightly testing (4 weeks
ago)
* 39c8acfed6 - HBASE-15151 ensure findbugs check runs in nightly tests on all
branches. (4 weeks ago)
* 8698e20768 - HBASE-18467 report nightly results to devs via jira (4 weeks ago)
* b325ae5593 - HBASE-20114 Fix IllegalFormatConversionException in rsgroup.jsp
Repplication. Was reverted earlier. (4 weeks ago)
* 1146625c4c - HBASE-20144 The shutdown of master will hang if there are no
live region server (4 weeks ago)
* 6e55325a80 - HBASE-20108 Remove jline exclusion from ZooKeeper (4 weeks ago)
| * dba480856b - (origin/branch-2) HBASE-20308 Dockerfile for test must include
git. (9 days ago)
| ... 115 commits
| * af9a108a93 - HBASE-19987 error-prone 2.2.0 (4 weeks ago)
| * ac18ae2722 - HBASE-20108 Remove jline exclusion from ZooKeeper (4 weeks ago)
|/
* 96a42b7359 - Revert "HBASE-20137 TestRSGroups is flakey" (4 weeks ago)
* f5c8713bdd - HBASE-20134 dev-support scripts should use mktemp instead of
hard-coding /tmp. (4 weeks ago)
... 6089 commits
* 5f3c0b7f9b - HBASE-11439 StripeCompaction may not obey the OffPeak rule to
compaction (Victor Xu) (3 years, 9 months ago)
* ba044f010e - HBASE-11435 Visibility labelled cells fail to getting
replicated. (Anoop) (3 years, 9 months ago)
* 0e8e41d0ef - HBASE-11355 a couple of callQueue related improvements (3 years,
9 months ago)
* 92c52a727a - Updated version in master to 2.0.0-SNAPSHOT after 'branch-1' is
created for 1.x line of releases (3 years, 9 months ago)
| * 6c98bff7b7 - (tag: rel/1.0.0, tag: 1.0.0RC5, tag: 1.0.0) Updated
CHANGES.txt for 1.0.0RC5 (3 years, 2 months ago)
| * 5fa72e0375 - Updated documentation (3 years, 2 months ago)
| * ecc7fb8ed1 - HBASE-13028 Cleanup MapReduce InputFormats (3 years, 2 months
ago)
| * 581770780b - Revert "HBASE-12867 Add ability to specify custom replication
endpoint to add_peer" (3 years, 2 months ago)
| * 255dc4e58a - HBASE-12971 Replication stuck due to large default value for
replication.source.maxretriesmultiplier. (3 years, 2 months ago)
... 927 commits
| * b59d931590 - HBASE-11439 StripeCompaction may not obey the OffPeak rule to
compaction (Victor Xu) (3 years, 9 months ago)
| * a02716fb45 - HBASE-11435 Visibility labelled cells fail to getting
replicated. (Anoop) (3 years, 9 months ago)
| * 9a6a59c7b7 - HBASE-11355 a couple of callQueue related improvements (3
years, 9 months ago)
|/
* 0167558eb3 - HBASE-11448 Fix javadoc warnings (3 years, 9 months ago)
* 34cd00b291 - HBASE-11443
TestIOFencing#testFencingAroundCompactionAfterWALSync times out (3 years, 9
months ago)
* 5af264c5b5 - HBASE-11335 Fix the TABLE_DIR param in TableSnapshotInputFormat
(deepankar) (3 years, 9 months ago)
* cfba8ccbad - HBASE-11433 LruBlockCache does not respect its configurable
parameters (3 years, 9 months ago)
... 8815 commits
* 948d0cdec4 - HADOOP-1045. Add contrib/hbase, a BigTable-like online
database. (11 years ago)
{code}
It's a bit out of date but gives a sense of scale. would be better to use
master instead of branch-2 I think? so we can see both amount of change 1 to 2
and amount of change while stabilizing 2 compared to the ~1k commits while
stabilizing 1?
> [2.0] Generate CHANGES.txt
> --
>
> Key: HBASE-18828
> URL: https://issues.apache.org/jira/browse/HBASE-18828
> Project: HBase
> Issue Type: Sub-task
>Reporter: stack
>Assignee: stack
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: changelog.md, hbase_branches.svg, releasenotes.md
>
>
> See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it
> into refguide while at it..)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[ https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428519#comment-16428519 ] Sean Busbey commented on HBASE-18828: - That seems like a reasonable enough request, but I don't see it at all in that visualization. unless I missed some major feature branch. Does the graph need all commits (ala git log --graph), or would something that elided series of commits within a branch be useful? That would show the commits where release branch splits happened. > [2.0] Generate CHANGES.txt > -- > > Key: HBASE-18828 > URL: https://issues.apache.org/jira/browse/HBASE-18828 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > Attachments: changelog.md, hbase_branches.svg, releasenotes.md > > > See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it > into refguide while at it..) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[ https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428413#comment-16428413 ] stack commented on HBASE-18828: --- bq. what is the visualization trying to say? Just picture of all branches (git log --graph is hard for me to trace). I want to dump in here path between 2.0.0 CHANGELOG and (I think) 1.0.0 CHANGELOG. We went via some 0.99 releases on our way from the merge-base to 1.0.0 (I'd forgotten) I think I have more work to do verifying. Will be back. > [2.0] Generate CHANGES.txt > -- > > Key: HBASE-18828 > URL: https://issues.apache.org/jira/browse/HBASE-18828 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > Attachments: changelog.md, hbase_branches.svg, releasenotes.md > > > See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it > into refguide while at it..) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[ https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428223#comment-16428223 ] Sean Busbey commented on HBASE-18828: - what is the visualization trying to say? > [2.0] Generate CHANGES.txt > -- > > Key: HBASE-18828 > URL: https://issues.apache.org/jira/browse/HBASE-18828 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > Attachments: changelog.md, hbase_branches.svg, releasenotes.md > > > See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it > into refguide while at it..) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[ https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428006#comment-16428006 ] stack commented on HBASE-18828: --- Need to tell a story on how hbase-2.0.0 relates to hbase-1.0.0 for CHANGELOG. Our branch history is kinda crazy. See attached hbase_branches.svg visualization made with git://github.com/esc/git-big-picture.git > [2.0] Generate CHANGES.txt > -- > > Key: HBASE-18828 > URL: https://issues.apache.org/jira/browse/HBASE-18828 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > Attachments: changelog.md, hbase_branches.svg, releasenotes.md > > > See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it > into refguide while at it..) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[
https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16427973#comment-16427973
]
stack commented on HBASE-18828:
---
Ok. Lets use yetus `releasedocmaker` going forward from hbase-2.0.0
(HBASE-14175). I'll check in its generated RELEASENOTES.md and CHANGELOG.md in
place of CHANGES.txt. `releasedocmaker` presumes JIRA is up to date and is
'source of truth'.
Here is how I did the "...validating the fix versions set in JIRA" suggested
over in HBASE-14025 with `releasedocmaker`. I copied and pasted Sean's recipe
from HBASE-14025 and updated it using 2.0.0 RC as version and amended
instruction so they fit making a major release rather than a point release as
HBASE-14025 details.
Of note, we branched 2.0.0 a long-time ago (4 years ago), at this point:
{code}
commit 0167558eb31ff48308d592ef70b6d005ba6d21fb
Author: Enis Soztutar
Date: Mon Jun 30 20:11:02 2014 -0700
HBASE-11448 Fix javadoc warnings
{code}
Next commit was {{92c52a727a Updated version in master to 2.0.0-SNAPSHOT after
'branch-1' is created for 1.x line of releases}}
Requires yetus install. See note at the bottom of yetus' downloads page for how
to do a homebrew install on your Mac (via [~busbey]) as well as his suggestion
that we rely on released versions of yetus.
# Clean up JIRA for your release
## Get the {{CHANGELOG.md}} and {{RELEASENOTES.md}} from JIRA; i.e. for 2.0.0:
{code}$ ./release-doc-maker/releasedocmaker.py -p HBASE --fileversions -v
2.0.0{code}. It is also possible to do release docs across a range of versions;
pass {code} --range --version START_VERSION --version END_VERSION{code}
## Filter the produced {{CHANGELOG.md}} so just a list of JIRA IDs {code}$ cat
CHANGELOG.md | grep -o -E "\[HBASE-[0-9]*\]" | grep -o -E "HBASE-[0-9]*" | sort
-u > CHANGELOG_jiras.txt{code}
## Get the set of JIRAs that are marked in git
### Find the commit where your release line branched off from the previous
release. {code}$ git merge-base origin/branch-1 origin/branch-2.0
0167558eb31ff48308d592ef70b6d005ba6d21fb{code:java}
### Get the set of all jiras committed between that branch point and current
branch tip (this is a deviation from Sean recipe. This is major version so all
changes since branch for previous major version). {code}$ git log --oneline
0167558eb31ff48308d592ef70b6d005ba6d21fb...3ee8b0c75b | grep -o -E
"^[0-9a-z]*\s*HBASE-[0-9]*"|awk '{print $2}' | sort -u > in_git_2.0.0.txt{code}
## Go through JIRAs that appear in the JIRA tracker but not in git {code}$ comm
-1 -3 in_git_2.0.0.txt CHANGELOG_jiras.txt{code}.
## * The commits may be in git but committed BEFORE the branch was made for
this release. Do not include these as part of this release.
## * Sometimes the format of the commit line is wrong (adjust your grep above
accordingly -- e.g. some committers add a '.' or a ':' after the JIRA ID).
##* sometimes these are issues that didn't get properly cleaned up when things
made it into the previous minor/major release during the RC process
##* sometimes they're task or umbrella jiras that don't have a representation
in git
##* sometimes they're documentation jiras that shouldn't have been marked for
the release (doc tickets always are resolved against the major version that was
in the _master_ git branch at the time)
##* sometimes they're improperly closed tickets (e.g. invalid, duplicate, and
wontfix tickets should not have a fix version)
##* sometimes they were improperly labeled on commit and weren't reverted and
reapplied with the correct commit message.
##* occasionally they're changes that should be in your branch but were missed.
in this case reopen the ticket and cherry-pick to your branch
## go through JIRAs that appear in git but not in JIRA {code}$ comm -2 -3
CHANGES_1.2.0_git.txt CHANGES_1.2.0_jira.txt {code}
##
*** sometimes these were improperly labeled on commit. ideally they will have
been reverted and reapplied with the correct commit message.
*** sometimes they weren't marked correctly in jira because they were pushed
out of the previous minor/major release during the RC process.
# remove entries in CHANGES.txt unrelated to your current release
** for a PATCH release, you should be starting from a file that only contains
related changes
** for a MINOR release, you should reset the file so that you will only have
changes for prior minor releases in the same major release (e.g. for the 1.2.0
release CHANGES.txt will start by copying the notes from 1.0.0 and 1.1.0)
** for a MAJOR release, you should reset the file so that you will only have
changes for prior major releases (e.g. for the 2.0.0 release CHANGES.txt will
start by copying the notes from 1.0.0)
# generate a post-clean-up set of text release notes from JIRA and add it to
the top of the CHANGES.txt file with the current date.
> [2.0] Generate CHANGES.txt
> --
>
>
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[
https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16409129#comment-16409129
]
stack commented on HBASE-18828:
---
Here are 'releasenotes' and 'changelog' generated via releasedocmaker (See
HBASE-14175) followed by:
ls -rd 2.0.0 1.* |xargs -t -I {} cat {}/CHANGELOG.md >> changelog.md
ls -rd 2.0.0 1.* |xargs -t -I {} cat {}/RELEASENOTES.md >> releasenotes.md
I attached result. Looks nice. Could switch to markdown for 2.0.0 and going
forward. Needs the HBASE-14025 verification work still. Presumes JIRA for old
releases is 'true' (has had the RM fixup).
> [2.0] Generate CHANGES.txt
> --
>
> Key: HBASE-18828
> URL: https://issues.apache.org/jira/browse/HBASE-18828
> Project: HBase
> Issue Type: Sub-task
>Reporter: stack
>Assignee: stack
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: changelog.md, releasenotes.md
>
>
> See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it
> into refguide while at it..)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-18828) [2.0] Generate CHANGES.txt
[ https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16408783#comment-16408783 ] stack commented on HBASE-18828: --- Just messed around with HBASE-14175 "Adopt releasedocmaker for better generated release notes". Also took a look again at notes in HBASE-14025. Let me play more w/ releasedocmaker. Need to minimally follow the suggested cleanup in HBASE-14025. Meantime, toward the goal of generating clean releasenotes/changes, I just did a first pass over JIRA where I did an mass-edit of fixedVersions in-line with the thinking expressed in HBASE-14025. * High-level I added 2.0.0 to issues that had only 2.0.0-beta-1 or 2.0.0-alpha-2, etc., as fixVersion so now they have 2.0.0 AND 2.0.0-beta-2. This way I can pull 2.0.0 from JIRA and it will include fixes in all alphas and betas too. * No JIRAs had 2.0.0-alpha-1 as fixVersion. Issues had 2.0.0 as their fix version at time of the 2.0.0-alpha-1 release. * Any 2.0.0 issue that also had 3.0.0 as fixVersion had the 3.0.0 removed (in the HBASE-14025 spirit. I was able to successfully generate 2.0.0 'release notes' from JIRA though there are thousands. TODO: Get HBASE-14025 notions into refguide. TODO: See if place for releasedocmaker. > [2.0] Generate CHANGES.txt > -- > > Key: HBASE-18828 > URL: https://issues.apache.org/jira/browse/HBASE-18828 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > > See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it > into refguide while at it..) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
