Hi, If the 2.8 release lead is not yet decided then I would like to take this opportunity. I want to learn about the background process of a release.
Regards, Pradeep On Fri, 23 Jan 2026 at 05:10, Madhan Neethiraj <[email protected]> wrote: > Rangers, > > Thank you for reviewing and your support for Ranger 2.8.0 release. 20+ > commits have landed since the start of this thread. It's time we plan the > release. I propose the following release plan: > > 1. 2.8.0 release will be from ranger-2.8 branch > 2. Jan-30, Friday: release branch will be closed for commits; commits > after this date will require approval from a PMC member > 3. Feb-03, Tuesday: release-candidate #0 will be out for vote by the > community > 4. Feb-10, Tuesday: tentative completion of the vote > 5. Feb-13, Friday: tentative release date > > If you are looking to include any fixes/updates in 2.8.0 release, please > make sure to land them in the release branch by Jan-30, Friday. > > Looking forward to your support in releasing Apache Ranger 2.8.0 as > planned. > > Thanks, > Madhan > > > On 1/7/26, 1:53 AM, "Mehul Parikh" <[email protected] <mailto: > [email protected]>> wrote: > > > Thanks Madhan. > > > +1 for Apache Ranger 2.8.0 release. > > > On Wed, Jan 7, 2026 at 6:57 AM Abhishek Kumar <[email protected] <mailto: > [email protected]>> wrote: > > > > Thanks Madhan for the initiative. > > > > +1 for Apache Ranger 2.8.0 release. > > > > On Tue, Jan 6, 2026 at 5:12 PM PradeeP AgrawaL < > > [email protected] <mailto:[email protected]>> > > wrote: > > > > > Thanks Madhan, > > > > > > +1 for Apache Ranger 2.8.0 release. > > > > > > > > > On Wed, 7 Jan 2026 at 00:13, Velmurugan Periasamy <[email protected] > <mailto:[email protected]>> > > wrote: > > > > > > > +1 for Apache Ranger 2.8.0 release. > > > > > > > > Thank you Madhan. > > > > > > > > On Tue, Jan 6, 2026 at 12:56 PM Ramesh Mani <[email protected] > <mailto:[email protected]>> wrote: > > > > > +1 for Apache Ranger 2.8.0 release activities. > > > > > > > > > > Thanks Madhan for initiating this. > > > > > > > > > > Regards, > > > > > Ramesh > > > > > > > > > > On Mon, Jan 5, 2026 at 10:53 PM Madhan Neethiraj < > [email protected] <mailto:[email protected]> > > > > <mailto:[email protected] <mailto:[email protected]>>> wrote: > > > > > > > > > > > Rangers, > > > > > > > > > > > > > > > > > > > > > > > > The community has added 75+ commits since Apache Ranger 2.7.0 > > release > > > > > > about 5 months back. Here are few enhancements/fixes in > ranger-2.8 > > > > branch: > > > > > > > > > > > > > > > > > > enhance policy engine to support service-managed ACLs > > (inline-policy) > > > > > > update Ozone authorizer to support AssumeRole operation > > > > > > service config UI updates to support service admin users and > groups > > > > > > fix issues in sending audit logs to Kerberized Solr > > > > > > Docker setup updates to use Kerberos authentication, latest Trino > > > > release > > > > > > fix tagsync module in HA deployment to avoid excessive CPU usage > > > > > > update plugins library to use the same user/group name > > transformation > > > > as > > > > > > usersync > > > > > > update audit logs retrieval API to support resource name > exclusion, > > > and > > > > > > sort by userId and action > > > > > > fix roles lookup API to apply role name filter for > role-membership > > as > > > > well > > > > > > add REST API to purge stale plugin info entries > > > > > > update YARN plugin to support fair scheduler > > > > > > policy engine enhancements to support synchronous policy cache > > > updates > > > > > > dependent component version updates: tomcat, netty, commons-lang, > > > > urllib3, > > > > > > axios > > > > > > I propose we get started on next release, Apache Ranger 2.8.0, to > > > > include > > > > > > above updates. Please share your thoughts. > > > > > > > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > > > Madhan > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Thanks and regards, > Mehul Parikh > ---------------------------- > M: +91 98191 54446 > E: [email protected] <mailto:[email protected]> > > > > >
