The issue is not in the product but in the report generation. It seems the
reporting tool does not work correctly on my new hardware. I ran it on
another machine and this one looks correct. I've updated the file, at the
same address [0].

This report shows a number of added methods, but still reports compatible.
Thus I'm upgrading my vote to +1.

[0]: http://people.apache.org/~ndimiduk/1.1.0_1.1.3RC0_compat_report.html

On Sun, Nov 15, 2015 at 3:18 PM, Andrew Purtell <andrew.purt...@gmail.com>
wrote:

> What is the specific compatibility issue?
>
> By default the tool will only look at classes we annotate as Public or
> LimitedPrivate. Maybe that's why some changes you are expecting to be
> called out are not present in the report?
>
>
> > On Nov 15, 2015, at 3:07 PM, Nick Dimiduk <ndimi...@apache.org> wrote:
> >
> > For my part, my vote is +0, pending review of compatibility report. My
> vote
> > is +1 assuming we can get a clean report.
> >
> > - download tarballs, verified signatures vs below ndimiduk.asc and KEYS
> > file in dist repo
> > - verified none of rej, orig, java, or scala files in the bin tgz
> > - verified none of rej, orig, class, jar files in the src tgz
> > - inspected site and docs in bin tgz, looks good
> > - build from source vs all combinations of openjdk-1.7.0_79,
> > openjdk-1.8.0_45, and hadoop versions 2.2.0, 2.3.0, 2.4.0, 2.4.1, 2.5.0,
> > 2.5.1, 2.5.2, 2.6.0, 2.6.1, 2.6.2, 2.7.0, 2.7.1
> > - ran in local mode with LoadTestTool, FAST_DIFF, 1mm rows; passed. I
> > noticed client connection log entries in the master .out file. I've never
> > noticed this; it was unexpected but not harmful.
> > - inspected linked compatibility report. I'm not convinced it is working
> > properly as even the acknowledged changes we observed in 1.1.2 [0] are
> not
> > reported. Thoughts Sean?
> > - ran stack's hbase-downstreamer [0] project `mvn clean package` vs
> staging
> > maven repo. Tests pass.
> > - ran Dmitry's shaded-client downstreamer project [1] vs staging maven
> repo
> > and bin tarball, versions adjusted for the release candidate. Test app
> runs
> > successfully.
> >
> > Thanks,
> > Nick
> >
> > [0]: https://github.com/saintstack/hbase-downstreamer
> > [1]: https://github.com/dminkovsky/HBASE-13889
> >
> >> On Thu, Nov 12, 2015 at 10:58 PM, Nick Dimiduk <ndimi...@apache.org>
> wrote:
> >>
> >> Thank you Josh for taking time to evaluate this release candidate. A
> >> reminder to others that the voting period is scheduled to expire in
> roughly
> >> 24 hours. I myself have not had time this week to evaluate this
> candidate
> >> properly, so I would like to extend the voting period through the
> weekend.
> >> If there are no objections I will tally the vote at 23:59 on Sunday,
> >> November 15, Pacific time.
> >>
> >> Thanks,
> >> Nick
> >>
> >>
> >>> On Tuesday, November 10, 2015, Josh Elser <josh.el...@gmail.com>
> wrote:
> >>>
> >>> +1 (non-binding)
> >>>
> >>> * Built from source
> >>> * Ran tests (-PrunDevTests). o.a.h.h.r.TestRegionServerHostname was
> >>> problematic, might have just been me.
> >>> * Checked sigs/xsums
> >>> * Checked the compat report (thanks for posting it, Nick)
> >>> * Skimmed release notes looking for anything that might introduce new
> >>> deps for licensing concerns (found none)
> >>>
> >>> Nick Dimiduk wrote:
> >>>
> >>>> I'm happy to announce the first release candidate of HBase 1.1.3
> >>>> (HBase-1.1.
> >>>> 3RC0) is available for download at
> >>>> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.1.3RC0/
> >>>>
> >>>> Maven artifacts are also available in the staging repository
> >>>>
> https://repository.apache.org/content/repositories/orgapachehbase-1117
> >>>>
> >>>> Artifacts are signed with my code signing subkey 0xAD9039071C3489BD,
> >>>> available in the Apache keys directory
> >>>> https://people.apache.org/keys/committer/ndimiduk.asc
> >>>>
> >>>> There's also a signed tag for this release at
> >>>>
> >>>>
> https://git-wip-us.apache.org/repos/asf?p=hbase.git;a=tag;h=16e905679e2dd5cb1b05ca8bc34a403e154a395f
> >>>>
> >>>> The detailed source and binary compatibility report vs 1.1.0 has been
> >>>> published for your review, at
> >>>> http://people.apache.org/~ndimiduk/1.1.0_1.1.3RC0_compat_report.html
> >>>>
> >>>> HBase 1.1.3 is the third patch release in the HBase 1.1 line,
> continuing
> >>>> on
> >>>> the theme of bringing a stable, reliable database to the Hadoop and
> NoSQL
> >>>> communities. This release includes over 120 bug fixes since the 1.1.2
> >>>> release. Notable correctness fixes
> >>>> include HBASE-14474, HBASE-14591, HBASE-14224,
> >>>> HBASE-14431, HBASE-14407, HBASE-14313, HBASE-14621, HBASE-14501, and
> >>>> HBASE-13250.
> >>>>
> >>>> The full list of fixes included in this release is available at
> >>>>
> >>>>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310753&version=12333152
> >>>>  and in the CHANGES.txt file included in the distribution.
> >>>>
> >>>> Please try out this candidate and vote +/-1 by 23:59 Pacific time on
> >>>> Friday, 2015-11-13 as to whether we should release these artifacts as
> >>>> HBase
> >>>> 1.1.3.
> >>>>
> >>>> Thanks,
> >>>> Nick
> >>>>
> >>>>
>

Reply via email to