If we develop good habit of regular releases, we normally won't need to hold the release train to get things in (except for critical security and correctness issues) as the next one is 2-3 months away.
On Fri, Jun 5, 2026 at 3:42 PM Neelesh Salian <[email protected]> wrote: > Hi folks, > > With 1.11.0 out the door, I want to open up the planning around 1.12.0. > As Steven noted on the dev list (thread for 1.11), 1.11.0 took roughly 8 > months from 1.10.0. This is longer than the 3-4 month cadence we have > previously discussed. > For 1.12.0 I'd like us to aim closer to that target. > > I'll be acting as the release manager for this release. Here are a few > notes to kick things off: > > - *Tentative release target: *late August / early September 2026 (~3 > months from 1.11.0). > - *Curation: *We'll use the June 24 community sync as the formal > kickoff to surface in-flight work and call out anything that should land in > this release. > - *Cadence reminder:* If something doesn't make it in 1.12, the next > one is ~3 months out (1.13). > - *Mid-cycle check-in: *I'll send a state-of-the-release update around > mid-July with what is in, what is in-flight, and what remains a blocker. > - *Tracking: *The open issues and PRs targeting this release are > tagged with the Iceberg 1.12.0 milestone > > <https://github.com/apache/iceberg/issues?q=milestone%3A%22Iceberg%201.12.0%22>. > I'll keep this milestone updated as things land in the repo. > > If you have a feature, fix, or breaking change you want considered for > 1.12.0, please reply on this thread or flag it on the June 24 sync. > > Thanks, > Neelesh >
