Hi PMC,
I've added my PGP key for Ranger 2.9.0 RM to dist/dev/ranger/KEYS
(revision 85777, key ID D49DAD7F7A2F45BC, [email protected]).
Could a PMC member please copy it to dist/release/ranger/KEYS before
RC0 vote on Jul 12?
Thanks,
Ram

On Wed, Jul 8, 2026 at 4:34 PM Ramachandran Krishnan <[email protected]>
wrote:

> Rangers,
>
> I am volunteering as Release Manager for Apache Ranger 2.9.0. Here is the
> proposed release plan:
>
>    1.
>
>    *Branch:* The ranger-2.9 branch will be used for this release.
>    2.
>
>    *Jul-11, Friday:* The release branch will be closed for commits. Any
>    commits after this date will require explicit approval from a PMC member.
>    3.
>
>    *Jul-12, Saturday:* Release Candidate #0 (RC0) will be cut and put up
>    for a community vote.
>    4.
>
>    *Jul-15, Tuesday:* Tentative completion of the vote (observing the
>    72-hour minimum).
>    5.
>
>    *Jul-17, Thursday:* Tentative official release date.
>
> If you want to include any fixes or updates in the 2.9.0 release, please
> make sure they land in the ranger-2.9 branch by *Friday, July 11*.
>
> Please object if you see issues with the timeline above, or flag any
> blocker tickets that must land before the branch lock.
>
>    -
>
>    *Release process documentation:*
>    https://apache.github.io/ranger/project/release-process/
>
> Looking forward to your support in getting Apache Ranger 2.9.0 out as
> planned.
>
> Thank you,
>
> *Ramachandran Krishnan*
>
> On Wed, Jul 8, 2026 at 3:12 PM Ramachandran Krishnan <[email protected]>
> wrote:
>
>>
>>
>> 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