Hi, I’m preparing the Apache Ranger 2.9.0 release (RM for RANGER-5670). Branch lock is done on ranger-2.9; RELEASE_NOTES are ready. I need the 2.9.0 Confluence release folder published on cwiki, matching the 2.8.0 layout <https://cwiki.apache.org/confluence/spaces/RANGER/pages/406620843/2.8.0+release+-+Apache+Ranger> .
could a RANGER space admin add my wiki user ramackri to the committer edit group (or grant Add page permission on the RANGER space)? I can login but get 403 when creating release pages under Release Folders. Regards, Ram On Sat, Jul 11, 2026 at 8:59 AM Ramachandran Krishnan <[email protected]> wrote: > Hi all, > The ranger-2.9 branch is now locked for the Apache Ranger 2.9.0 release. > After this notice, only blocker or critical fixes will be considered for > ranger-2.9, and those require PMC approval. > Planned schedule: > - Jul 11 (evening): version bump to 2.9.0 > - Jul 12: RC0 build, sign, upload, [VOTE] email (72 hours) > - Jul 17: GA target > Release tracking: https://issues.apache.org/jira/browse/RANGER-5670 > Thanks, > Ram > > On Fri, Jul 10, 2026 at 10:46 AM Ramachandran Krishnan <[email protected]> > wrote: > >> Hi All, >> Apache Ranger 2.9.0 release work has started. We plan to lock the >> ranger-2.9 >> branch tomorrow (Jul 11, 2026), cut RC0 on Jul 12, and target GA on Jul >> 17. >> If you have any open pull requests or fixes intended for 2.9.0, please >> ensure >> they are raised against ranger-2.9 and reviewed by end of day today (Jul >> 10). >> After branch lock, only blocker or critical fixes will be considered, and >> those require PMC approval. >> Please speak up today if you need a change included in 2.9.0. Otherwise we >> will proceed with branch lock and RC0 on schedule. >> Release tracking: https://issues.apache.org/jira/browse/RANGER-5670 >> Thanks, >> Ramachandran Krishnan >> >> On Wed, Jul 8, 2026 at 8:12 PM Ramachandran Krishnan <[email protected]> >> wrote: >> >>> 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 >>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>> > >>>>> >>>>
