+1 (Binding)

Tested against hbase-1.3 and hbase-1.6

* Build from source (mvn clean install -DskipTests
-Dhbase.profile=1.3/1.6): OK
* Did some basic DDL, queries, upserts, deletes and everything looked fine:
OK
* Did some upgrade testing: Create tables, views, indices from an old
client, query, upsert. Then upgrade to 4.16 metadata, query, upsert from an
old client, then upgrade the client and query, upsert from a new client: OK
* Verified checksums: OK
* Verified signatures: OK
* mvn clean apache-rat:check: OK

On Sun, Feb 21, 2021 at 7:54 AM Josh Elser <[email protected]> wrote:

> Be sure to update
> https://dist.apache.org/repos/dist/release/phoenix/KEYS with your key
> prior to releasing this.
>
> +1 (binding)
>
> * Sigs/xsums are good
> * No unexpected files in source release
> * rat:check passes
> * Build from src, ran against 1.4.13
>
> On 2/16/21 12:08 AM, Xinyi Yan wrote:
> > Hello Everyone,
> >
> > This is a call for a vote on Apache Phoenix 4.16.0 RC3. This is the next
> > minor release of Phoenix 4, compatible with Apache HBase 1.3, 1.4, 1.5
> > and 1.6.
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache phoenix 4.16.0
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 4.16.0RC3
> > https://github.com/apache/phoenix/tree/4.16.0RC3
> >
> > The release files, including signatures, digests, as well as CHANGES.md
> > and RELEASENOTES.md included in this RC can be found at:
> > <https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.16.0RC2/>
> > https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.16.0RC3
> >
> > For a complete list of changes, see:
> > <
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.16.0RC2/CHANGES.md
> >
> >
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.16.0RC3/CHANGES.md
> >
> > Artifacts are signed with my "CODE SIGNING KEY":
> > E4882DD3AB711587
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/dev/phoenix/KEYS
> >
> >
> > Thanks,
> > Xinyi
> >
>


-- 
Chinmay Kulkarni

Reply via email to