Had some chats with my colleagues today. Looks like STS support is something we'd like to ship soon. It will expand our community because projects like Apache Polaris require STS for object store. If we can ship STS in 2.2.0 in the next few months it'll make a lot of people happy.
Also: JDK17 requirement <https://issues.apache.org/jira/browse/HDDS-14439> for Ozone service roles. This is big. Do we want it in Ozone 2.2.0 too? On Fri, Jan 16, 2026 at 7:14 PM Wei-Chiu Chuang <[email protected]> wrote: > The onprem Ozone installer is another great addition in 2.2.0. A huge step > towards simplifying installation. > > https://issues.apache.org/jira/browse/HDDS-13870 > > On Mon, Jan 12, 2026 at 1:28 PM Wei-Chiu Chuang <[email protected]> > wrote: > >> With the version 2.1.0 behind us, it's time to talk about the next >> release to keep the momentum going. >> >> What do we want in this release? I see a number of features are making >> good progress: >> >> 1. the disk balancer just got merged. >> 2. AWS STS support -- i know there's a strong push to get it out soon. >> 3. Event Notification >> 4. S3 Lifecycle Configurations seems to be near completion. >> 5. short circuit read >> 6. Ozone Snapshot Defragmentation >> >> Small features >> 7. new readBlock API (HDDS-10338 >> <https://issues.apache.org/jira/browse/HDDS-10338>) >> 8. high performance vectored read API HDDS-13660 >> <https://issues.apache.org/jira/browse/HDDS-13660> >> >> If we can get 2-3 features ready, that's enough to make another release. >> Ozone 2.0 was announced on April 30. It'd be great to have a 2.2 release in >> April too. >> >> Thoughts and suggestions? >> >
