+1 for ranger 2.9.0-rc3 release.

Thanks Ram for driving the release efforts.

Thanks,
Selva-

> On Jul 31, 2026, at 6:48 AM, Ramachandran Krishnan <[email protected]> wrote:
> 
> Hi Rangers,
> 
> Apache Ranger 2.9.0 release candidate #3 is now available for a vote within
> the dev community. RC3 is built from a fresh git clone of ranger-2.9 at
> f39599d78. Links to all the release artifacts are given below. Please take
> some time to review and vote.
> 
> The vote will be open for at least 72 hours or until necessary votes are
> reached.
> 
>   [ ] +1 approve
>   [ ] +0 no opinion
>   [ ] -1 disapprove (and reason why)
> 
> Changes since RC2 (release-2.9.0-rc2):
> 
> - RANGER-5712: Fix Trino/Ozone plugin auth in ranger-docker (Kerberos keytabs,
>   policy download auth, Solr audit JAAS for Ozone)
> - RANGER-5716: Fix swapped client IP and resource in KMS Ranger audits
> 
> Link of all Issues/Improvements addressed in this release:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20RANGER%20AND%20fixVersion%20%3D%202.9.0%20ORDER%20BY%20summary%20ASC%2C%20priority%20DESC%2C%20updated%20DESC
> 
> Git tag for the release:
> https://github.com/apache/ranger/releases/tag/release-2.9.0-rc3
> 
> Sources for the release:
> https://dist.apache.org/repos/dist/dev/ranger/2.9.0-rc3/apache-ranger-2.9.0.tar.gz
> 
> Source Release Verification:
> 
> PGP signature:
> https://dist.apache.org/repos/dist/dev/ranger/2.9.0-rc3/apache-ranger-2.9.0.tar.gz.asc
> SHA512 Hash:
> https://dist.apache.org/repos/dist/dev/ranger/2.9.0-rc3/apache-ranger-2.9.0.tar.gz.sha512
> SHA256 Hash:
> https://dist.apache.org/repos/dist/dev/ranger/2.9.0-rc3/apache-ranger-2.9.0.tar.gz.sha256
> 
> Checksum (apache-ranger-2.9.0.tar.gz):
> SHA256: 03320fef7f2c77cd6f6fac8a4207a94b53da131bcd85eb64b00949b61ad65f11
> 
> Keys to verify the signature of the release artifacts are available at:
> https://dist.apache.org/repos/dist/release/ranger/KEYS
> 
> Release Notes:
> https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+2.9.0+-+Release+Notes
> 
> Thanks,
> Ram

Reply via email to