[
https://issues.apache.org/jira/browse/HBASE-18276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606727#comment-16606727
]
Sean Busbey commented on HBASE-18276:
-------------------------------------
Now have a clean nightly build from yesterday:
https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/460/
and the flaky list looks like flakies rather than always-failing things:
https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/job/branch-1.2/26/artifact/dashboard.html
I've just pushed an updated CHANGES file again.
Here's the updated command I used to get the list of issues covered in git:
{code}
git log --oneline rel/1.2.6...branch-1.2 | grep -o -E
'(^[a-z0-9]{10}|[bB]ackport) HBASE-[0-9]*[:,.]? ' | grep -o -E 'HBASE-[0-9]*' |
sort -u >
/path/to/some/staging/directory/for/hbase-release-1.2/CHANGES_1.2.7_git.txt
{code}
after cleaning up jira, the following are just noted here:
in jira but not in git
* HBASE-18266 - umbrella
* HBASE-18277 - infra only change
* HBASE-19204 - umbrella
* HBASE-20004 - bad commit message on branch-1.2
* HBASE-20062 - infra only change
* HBASE-21059 - umbrella
* HBASE-21060 - backports that didn't note the backport jira in commit messages
in git but not in jira
* HBASE-14498 - reverted
* HBASE-17425 - reverted
* HBASE-17876 - previous release tracker
* HBASE-18267 - reverted
I ran a compatibility report in prep for RC
{code}
dev-support busbey$ ./checkcompatibility.py --annotation
org.apache.hadoop.hbase.classification.InterfaceAudience.LimitedPrivate
--annotation org.apache.hadoop.hbase.classification.InterfaceAudience.Public
rel/1.2.6 branch-1.2
...
INFO:root:Results: {'binary': {'problems': 14, 'warnings': 2}, 'source':
{'problems': 14, 'warnings': 0}}
ERROR:root:Found problems during binary check (known issues: 0, observed
issues: 14)
ERROR:root:Found problems during source check (known issues: 0, observed
issues: 14)
{code}
The report shows 13 removed methods caused by HBASE-20884. I agree the change
is a good idea with a reasonable mitigation plan for downstream covered in the
release note.
It also shows 1 method changed incompatibly for the Scan class after
HBASE-17617. I think this is a false positive and have filed
[lvc/japi-compliance-checker/#50|https://github.com/lvc/japi-compliance-checker/issues/50]
for it. Details about what's reported and why it's wrong are on that issue.
> Release 1.2.7
> -------------
>
> Key: HBASE-18276
> URL: https://issues.apache.org/jira/browse/HBASE-18276
> Project: HBase
> Issue Type: Task
> Components: community
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Major
> Fix For: 1.2.7
>
>
> about time to get rolling on 1.2.7 for ~monthly
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
