What we want to do here? Sink the RC and work on fixing a few of the flakies? TestMasterFailoverWithProcedures and TestMasterFailoverWithProcedures? They fail rarely enough up on apache [1] and our flakies list is pretty bare these times on branch-2.0 [1].
Thanks, S 1. https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/job/branch-2.0/lastSuccessfulBuild/artifact/dashboard.html On Sun, Nov 25, 2018 at 4:22 PM Stack <st...@duboce.net> wrote: > The first release candidate for HBase 2.0.3 is available for download: > > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.3RC0/ > > Maven artifacts are also available in a staging repository at: > > https://repository.apache.org/content/repositories/orgapachehbase-1237 > > Artifacts are signed with my key (DB9D313DA7874F29) published in our > KEYS file at http://www.apache.org/dist/hbase/KEYS > > The RC corresponds to the signed tag 2.0.3RC0, which currently points > to commit > > 87a3aea8ee2d284807f7d4fbdac1f6d9dfedbc17 > > HBase 2.0.3 is the third maintenance release in the HBase 2.0 line, > continuing on the theme of bringing a stable, reliable database to > the Hadoop and NoSQL communities. This release includes ~120 bug > and improvements fixes done since the 2.0.2 release almost 3 months > ago. > > The detailed source and binary compatibility report vs 2.0.2 has been > published for your review, at: > > > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.3RC0/compat-check-report-2.0.2-vs-2.0.3.html > > The report shows no incompatibilities. > > The full list of fixes included in this release is available in > the CHANGES.md that ships as part of the release also available > here: > > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.3RC0/CHANGES.md > > The RELEASENOTES.md are here: > > > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.3RC0/RELEASENOTES.md > > Please try out this candidate and vote +1/-1 on whether we should > release these artifacts as HBase 2.0.3. > > The VOTE will remain open for at least 72 hours. Given sufficient votes > I would like to close it on Thursday, November 29th, 2018. > > Thanks, > S >