Yeah, that's my intent.

On Tue, Aug 18, 2015 at 11:42 PM, Andrew Purtell <andrew.purt...@gmail.com>
wrote:

> This vote is going to pass without an actual veto. Assuming that's the
> intent and these details can be fixed for 1.1.3.
>
>
> > On Aug 18, 2015, at 7:29 PM, Sean Busbey <bus...@cloudera.com> wrote:
> >
> > currently -0 for
> >
> > * HBASE-14245 Incorrect LICENSE / NOTICE files for Netty 3 bundling
> > * HBASE-14244 hbase-resource-bundle jar missing copyright end year
> >
> > but so far looks unaffected by HBASE-14243. will try to finish looking at
> > rest of license by cut off.
> >
> >> On Tue, Aug 18, 2015 at 12:27 PM, Nick Dimiduk <ndimi...@apache.org>
> wrote:
> >>
> >> +1
> >>
> >> - 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.85, openjdk-1.8.0.51-0.b16, 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.7.0, 2.7.1
> >> - ran in local mode with LoadTestTool, FAST_DIFF, 1mm rows (about an
> hour).
> >> passed.
> >> - ran rolling upgrade from 0.98.0 on 7-node cluster while running LTT
> from
> >> 0.98.0 client. Ran to completion without incident, though I did file a
> >> minor ticket after inspecting the logs (HBASE-14240).
> >> - inspected linked compatibility report. Nothing changed since 1.1.1RC0
> >> report.
> >> - 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, following instructions similar to those found in my
> JIRA
> >> comment [2], versions adjusted for the release candidate. Test app runs
> >> successfully.
> >>
> >> [0]: https://github.com/saintstack/hbase-downstreamer
> >> [1]: https://github.com/dminkovsky/HBASE-13889
> >> [2]:
> >>
> >>
> https://issues.apache.org/jira/browse/HBASE-13889?focusedCommentId=14692493&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14692493
> >>
> >>> On Thu, Aug 13, 2015 at 2:21 PM, Nick Dimiduk <ndimi...@apache.org>
> wrote:
> >>>
> >>> I'm happy to announce the first release candidate of HBase 1.1.2
> >>> (HBase-1.1.2RC0) is available for download at
> >>> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.1.2RC0/
> >>>
> >>> Maven artifacts are also available in the staging repository
> >>> https://repository.apache.org/content/repositories/orgapachehbase-1090
> >>>
> >>> 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=c4b4a91620639fd964444e59171369c630dc51e3
> >>>
> >>> 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.2RC0_compat_report.html
> >>>
> >>> HBase 1.1.2 is the second 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 70 bug fixes since the
> >> 1.1.1
> >>> release. Notable correctness fixes include HBASE-14054, HBASE-12865,
> >>> HBASE-13993, HBASE-13337, HBASE-14013, HBASE-13895.
> >>>
> >>> The full list of fixes included in this release is available at
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310753&version=12332793
> >>> and in the CHANGES.txt file included in the distribution.
> >>>
> >>> Please try out this candidate and vote +/-1 by midnight Pacific time on
> >>> Monday, 2015-08-17 as to whether we should release these artifacts as
> >> HBase
> >>> 1.1.2.
> >>>
> >>> Thanks,
> >>> Nick
> >
> >
> >
> > --
> > Sean
>



-- 
Sean

Reply via email to