Pushed. That's the last blocker that I know of.

On Tue, Jan 26, 2016 at 6:22 PM, Elliott Clark <ecl...@apache.org> wrote:

> I think that one should land today, as the last flakey test has been
> removed and I've got a +1.
>
> On Tue, Jan 26, 2016 at 2:19 PM, Sean Busbey <bus...@cloudera.com> wrote:
>
>> Hi Jerry!
>>
>> I've been waiting for us to run out of blockers. Thus far we've always
>> ended up with another one opened before I could roll an RC after prior
>> ones
>> close.
>>
>> Here's a filter:
>>
>> *http://s.apache.org/hbM <http://s.apache.org/hbM>*
>>
>> at the moment I'm waiting on HBASE-15146.
>>
>>
>>
>> On Tue, Jan 26, 2016 at 1:41 PM, Jerry He <jerry...@gmail.com> wrote:
>>
>> > Hi, Sean
>> >
>> > Are you planning to get another RC out soon?  HBASE-14962 has been
>> > resolved.
>> >
>> > Thanks.
>> >
>> > On Mon, Jan 11, 2016 at 2:52 PM, Sean Busbey <bus...@cloudera.com>
>> wrote:
>> >
>> > > Vote tally:
>> > >
>> > > +1 (binding) : 1
>> > >  -1 (binding) : 1
>> > >
>> > > This vote fails.
>> > >
>> > > Thanks for everyone who took a look. I'll spin another RC once
>> > HBASE-14962
>> > > is either resolved or moved out of 1.2.0 (presuming no other blockers
>> > come
>> > > up).
>> > >
>> > > -Sean
>> > >
>> > > On Sun, Jan 3, 2016 at 6:29 AM, Sean Busbey <bus...@apache.org>
>> wrote:
>> > >
>> > > > Happy New Year everyone! I'm pleased to announce the first release
>> > > > candidate for HBase 1.2.0.
>> > > >
>> > > > Artifacts are available here:
>> > > >
>> > > > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.2.0RC0/
>> > > >
>> > > > As of this vote, the relevant md5 hashes are:
>> > > > 41c499a325ae6449fe99bbe315d07e10  hbase-1.2.0-bin.tar.gz
>> > > > 537874610f1b53d4bce9d8a925661246  hbase-1.2.0-src.tar.gz
>> > > >
>> > > > Maven artifacts are also available in the staging repository:
>> > > >
>> > > >
>> > https://repository.apache.org/content/repositories/orgapachehbase-1122/
>> > > >
>> > > > artifacts are signed with my code signing key 0D80DB7C, available in
>> > > > the project KEYS file:
>> > > >
>> > > > http://www.apache.org/dist/hbase/KEYS
>> > > >
>> > > > these artifacts correspond to commit hash
>> > > >
>> > > > 20c4368065165ad49bdfe8172316e42566a6d6a0
>> > > >
>> > > > which signed tag 1.2.0RC0 currently points to
>> > > >
>> > > >
>> > > >
>> > >
>> >
>> https://git1-us-west.apache.org/repos/asf?p=hbase.git;a=tag;h=771e13960cf406185bb29447dffb6f2b5a56baec
>> > > >
>> > > > HBase 1.2.0 is the second minor release in the HBase 1.x line,
>> > continuing
>> > > > on
>> > > > the theme of bringing a stable, reliable database to the Hadoop and
>> > NoSQL
>> > > > communities. This release includes roughly 250 resolved issues not
>> > > covered
>> > > > by previous 1.x releases.
>> > > >
>> > > > Notable new features include:
>> > > > - JDK8 is now supported
>> > > > - Hadoop 2.6.1+ and Hadoop 2.7.1+ are now supported
>> > > > - per column-family time ranges for scan (HBASE-14355)
>> > > > - daemons respond to SIGHUP to reload configs (HBASE-14529)
>> > > > - region location methods added to thrift2 proxy (HBASE-13698)
>> > > > - table-level sync that sends deltas (HBASE-13639)
>> > > > - client side metrics via JMX (HBASE-12911)
>> > > >
>> > > > The full list of issues can be found at:
>> > > >
>> > > >
>> > > >
>> > >
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310753&version=12332062
>> > > >
>> > > > Please take a few minutes to verify the release[1] and vote on
>> > releasing
>> > > > it:
>> > > >
>> > > > [ ] +1 Release this package as Apache HBase 1.2.0
>> > > > [ ] +0 no opinion
>> > > > [ ] -1 Do not release this package because...
>> > > >
>> > > > Vote will be subject to Majority Approval[2] and will close at
>> 8:00PM
>> > > > UTC on Monday, Jan 11th, 2016[3].
>> > > >
>> > > > [1]: http://www.apache.org/info/verification.html
>> > > > [2]:
>> https://www.apache.org/foundation/glossary.html#MajorityApproval
>> > > > [3]: to find this in your local timezone see:
>> > > > http://s.apache.org/hbase-1.2.0-rc0-close
>> > > >
>> > >
>> > >
>> > >
>> > > --
>> > > Sean
>> > >
>> >
>>
>>
>>
>> --
>> Sean
>>
>
>

Reply via email to