Checked the recent commits in
https://gitbox.apache.org/repos/asf?p=hbase.git;a=shortlog;h=refs/heads/branch-2.2.
I thought there are no critical changes since 2.2.0RC5.

张铎(Duo Zhang) <palomino...@gmail.com> 于2019年6月11日周二 上午9:08写道:

> Are there any critical changes recently?
>
> Guanghao Zhang <zghao...@gmail.com> 于2019年6月11日周二 上午8:54写道:
>
> > >
> > > The only RN is on HBASE-21075, which
> > > does not carry a fix version of 2.2.0.
> > >
> > HBASE-21075 is only committed to branch-2.0 and branch-2.1. It is a issue
> > for 2.0 and 2.1, not for 2.2. So the fix version didn't contains 2.2.0.
> >
> > Two possible fixes: add 2.2.0
> > > as a fixversion for HBASE-21075, or copy the RN to HBASE-21970
> > >
> > HBASE-21970 is the document about how to upgrade from 2.0 or 2.1 to 2.2+.
> > It is not enought? Let me copy the document to the RN to HBASE-21970.
> >
> >  If this is
> > > OK, I think we could make a RC6 with the release note change
> > >
> > Need to roll a new RC if only change the release note? Roll a new RC will
> > contain recent commits on branch-2.2, too.
> >
> >
> > 张铎(Duo Zhang) <palomino...@gmail.com> 于2019年6月11日周二 上午8:19写道:
> >
> > > Maybe we could amend the release note for HBASE-21075 to HBASE-20881?
> Or
> > at
> > > least reference HBASE-21075 in the release note for HBASE-20881? If
> this
> > is
> > > OK, I think we could make a RC6 with the release note change and give
> it
> > a
> > > one day vote window, if no objections we can push the release out.
> > >
> > > Sean Busbey <bus...@apache.org> 于2019年6月11日周二 上午12:14写道:
> > >
> > > > -1
> > > >
> > > > (reminder that -1s are not vetos on release votes)
> > > > bad:
> > > > * Release notes still have no call out / warning for folks about the
> > > > procedure needed to doing a rolling upgrade from earlier versions due
> > > > to the changes in HBASE-20881. The only RN is on HBASE-21075, which
> > > > does not carry a fix version of 2.2.0. Two possible fixes: add 2.2.0
> > > > as a fixversion for HBASE-21075, or copy the RN to HBASE-21970
> > > >
> > > > good:
> > > > * checksums fine
> > > > * signatures fine
> > > > * LICENSE/NOTICE in src, bin, and client-bin artifacts
> > > > * source corresponds to 2.2.0RC5 tag
> > > >
> > > > On Tue, Jun 4, 2019 at 6:11 AM Guanghao Zhang <zghao...@gmail.com>
> > > wrote:
> > > > >
> > > > > Please vote on this release candidate (RC) for Apache HBase 2.2.0.
> > > > > This is the first release of the branch-2.2 line.
> > > > >
> > > > > The VOTE will remain open for at least 72 hours.
> > > > >
> > > > > [] +1
> > > > > [] +0/-0
> > > > > [] -1 Do not release this package because ...
> > > > >
> > > > > The tag to be voted on is 2.2.0-RC5. The release files, including
> > > > > signatures, digests, etc. can be found at:
> > > > > https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC5/
> > > > >
> > > > > Maven artifacts are available in a staging repository at:
> > > > >
> > >
> https://repository.apache.org/content/repositories/orgapachehbase-1316/
> > > > >
> > > > > Signatures used for HBase RCs can be found in this file:
> > > > > https://dist.apache.org/repos/dist/release/hbase/KEYS
> > > > >
> > > > > The list of bug fixes going into 2.2.0 can be found in included
> > > > > CHANGES.md and RELEASENOTES.md available here:
> > > > > https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC5/CHANGES.md
> > > > > <https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC4/CHANGES.md>
> > > > >
> > https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC5/RELEASENOTES.md
> > > > > <
> > https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC4/RELEASENOTES.md
> > > >
> > > > >
> > > > > A detailed source and binary compatibility report for this release
> is
> > > > > available at
> > > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC5/api_compare_2.2.0RC5_to_2.1.4.html
> > > > > <
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC4/api_compare_2.2.0RC4_to_2.1.4.html
> > > > >
> > > > >
> > > > > To learn more about Apache HBase, please see
> > http://hbase.apache.org/
> > > > >
> > > > > Thanks,
> > > > > Guanghao Zhang
> > > >
> > >
> >
>

Reply via email to