Hi Nicholas, That's the issue - STS can't go into 2.2.0 because it requires Ranger changes, and those Ranger changes require an Ozone release for the commit I posted.
That's why I was wondering if the commit I posted could be released in Ozone 2.1.1 and then STS in Ozone 2.2.0 (when the upgraded Ranger is complete). But from what Sammi mentioned, it looks like the commit needs to go in Ozone 2.2.0 and then STS released in 2.3.0 (again when the upgraded Ranger is complete). Fabian On Sat, May 9, 2026 at 9:11 AM Tsz Wo Sze <[email protected]> wrote: > Hi Fabian, > > Since STS is a new feature, it is better to go to 2.2.0 (a minor release) > but not 2.1.1 (a maintenance/bug fix release). > > Tsz-Wo > > > > On Fri, May 8, 2026 at 6:52 AM Fabian Morgan <[email protected]> wrote: > > > Hi Sammi, > > > > Thanks for the info. I wasn't sure if point releases are faster than > main > > ones and/or if one was planned soon. > > > > Thanks, > > > > Fabian > > > > On Fri, May 8, 2026 at 1:41 AM Sammi Chen <[email protected]> wrote: > > > > > Fabian, > > > > > > Ozone 2.2.0 release is under discussion. Based on current status, it > > likely > > > can be released in June. > > > > > > Sammi > > > > > > On Fri, 8 May 2026 at 06:55, Fabian Morgan <[email protected]> > wrote: > > > > > > > Hi all, > > > > > > > > This commit (https://github.com/apache/ozone/pull/10108) is a > > necessary > > > > dependency for the Ranger team to implement changes required in turn > > for > > > > the Ozone STS feature. Is there a (fairly soon) upcoming Ozone > release > > > > vehicle this commit can be placed in, so that the Ranger team can be > > > > unblocked? Perhaps Ozone 2.1.1? > > > > > > > > Thanks! > > > > > > > > Fabian > > > > > > > > > >
