Hello Everyone,

This is a call for a vote on PhoenixDB 1.2.2 RC0.

PhoenixDB is native Python driver for accessing Phoenix via Phoenix Query
Server.

This version contains the following improvements compared to the previous
1.2.1 release

- Update python-phoenixdb/RELEASING.rst (PHOENIX-6820)
- Crash Due to Unhandled JDBC Type Code 0 for NULL Values (PHOENIX-7246)
- Manage requests-gssapi version for Phython 3.7 and lower (PHOENIX-7221)
- Add Python 3.11 to supported languages and update docker test image for
phoenixdb (PHOENIX-6858)
- Add Python 3.12 to supported versions and the test matrix (PHOENIX-7222)
- Document workaround for PhoenixDB 1.2+ not working with Python2 on some
systems (PHOENIX-6863)
- Update install instructions in README.rst (PHOENIX-6812)
- Add support for SQLAlchemy 2.0 (PHOENIX-6892)
- SQLAlchemy is no longer an install dependency (PHOENIX-6892)
- Run tests with all supported Python + SqlAlchemy versions (1.3, 1.4, 2.0)
(PHOENIX-6892)
- Replace deprecated failUnless methods in tests (PHOENIX-6892)
- Add support for specifying custom HTTP headers (PHOENIX-6921)
- Use JDBC/Avatica column label as column name when set (PHOENIX-6917)
- Do not throw exception when shutting down Python with open connections
(PHOENIX-6926)

The source release consists of the contents of the python-phoenixdb
directory of the phoenix-queryserver repository.

The source tarball, including signatures, digests, etc can be found at:

https://dist.apache.org/repos/dist/dev/phoenix/python-phoenixdb-1.2.2.rc0/src/

Artifacts are signed with my (Richard Antal) "CODE SIGNING KEY":
7813862A85AFBBB4FE71CC95E7B87AA3FFA8EDAD

KEYS file available here:
https://dist.apache.org/repos/dist/release/phoenix/KEYS

The hash and tag to be voted upon:

https://github.com/apache/phoenix-queryserver/tree/b1c2d2c5a24bdc8141570d3b626bd4cf1bae6e5b


https://github.com/apache/phoenix-queryserver/tree/python-phoenixdb-1.2.2.rc0

The vote will be open for at least 72 hours. Please vote:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Thanks,
Richard

Reply via email to