On 2026/07/08 09:40:32 Ramachandran Krishnan wrote:
> sure Madhan
> 
> On 2026/07/06 23:30:46 Madhan Neethiraj wrote:
> > Ram,
> > 
> > Thank you for volunteering to be the release manager for 2.9.0. Please 
> > review release process details at 
> > https://apache.github.io/ranger/project/release-process/. Let's target the 
> > release by July-17, which would require the release branch to be locked by 
> > end of this week.
> > 
> > Thanks,
> > Madhan
> > 
> > 
> > On 7/3/26, 9:52 AM, "Ramachandran Krishnan" <[email protected] 
> > <mailto:[email protected]>> wrote:
> > 
> > 
> > Hi,
> > If the 2.9 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,
> > Ram
> > 
> > 
> > On 2026/06/08 17:15:56 Madhan Neethiraj wrote:
> > > Rangers,
> > > 
> > > I propose we target 2.9.0 release for June-30. Please share your thoughts.
> > > 
> > > Thanks,
> > > Madhan
> > > 
> > > On 4/28/26, 12:35 PM, "Madhan Neethiraj" <[email protected] 
> > > <mailto:[email protected]> <mailto:[email protected] 
> > > <mailto:[email protected]>>> wrote:
> > > 
> > > 
> > > Rangers,
> > > 
> > > The community has added 30+ commits since 2.8.0 release couple of months 
> > > back, including the following: 
> > > 
> > > - PDP (policy decision point) server implementation
> > > - PDP client in Python and Java
> > > - support for HTTP header-based authentication
> > > - reduced library dependency for ranger-plugins-common library
> > > - tagsync update to support Trino 
> > > - Polaris service-def updates
> > > - dependent components version updates
> > > 
> > > I propose we get started on next release, Apache Ranger 2.9.0, to include 
> > > above updates, with tentative release date of May-15. If you would like 
> > > to include any fixes or enhancements in this release, please align with 
> > > this timeline.
> > > 
> > > Thanks,
> > > Madhan
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > 
> > 
> > 
> > 
> > 
> 

Reply via email to