> > I created a PR to fix that: https://github.com/apache/polaris/pull/4430 > I will resume the release process as soon as this PR is merged.
Hi, JB I have reviewed and approved to unblock this release. Thanks for the PR. - Ajantha On Thu, May 14, 2026 at 11:38 AM Jean-Baptiste Onofré <[email protected]> wrote: > Hi everyone, > > As discussed, I started the release process for 1.5.0. > > However, the step 3 of the process (build & publish) failed on the Python > CLI publication. > > I created a PR to fix that: https://github.com/apache/polaris/pull/4430 > > I will resume the release process as soon as this PR is merged. > > Regards > JB > > On Wed, May 13, 2026 at 6:44 AM Jean-Baptiste Onofré <[email protected]> > wrote: > > > Hi everyone, > > > > I have completed the triage of GitHub issues and PRs, moving stale items > > to the 1.6.0 milestone. > > > > Currently, there are no remaining issues or PRs assigned to the 1.5.0 > > milestone. I plan to start the 1.5.0 release process tonight (my time). > > > > If there is anything else you would like to include, please let me know. > > > > Regards, > > JB > > > > On Tue, May 12, 2026 at 5:16 AM Jean-Baptiste Onofré <[email protected]> > > wrote: > > > >> Hi everyone > >> > >> I plan to cut the 1.5.0 release on vote on Wednesday night or Thursday > >> morning my time. > >> > >> Please update the milestone on GitHub. I will do triage today. > >> > >> Thanks! > >> > >> Regards > >> JB > >> > >> Le jeu. 7 mai 2026 à 00:07, Dmitri Bourlatchkov <[email protected]> a > >> écrit : > >> > >>> Hi All, > >>> > >>> I believe it is best to re-establish a predictable release cadence for > >>> May. > >>> I see users wondering about that (e.g. in slack). If we have to exclude > >>> Iceberg 1.11 to get a quicker 1.5.0 release, it will be reasonable from > >>> my > >>> POV. > >>> > >>> Cheers, > >>> Dmitri. > >>> > >>> On Wed, May 6, 2026 at 5:41 AM Robert Stupp <[email protected]> wrote: > >>> > >>> > Hi all, > >>> > > >>> > +1 on 1.5.0 next week. > >>> > > >>> > I also second Alex' point, so +1 on excluding Iceberg 1.11.0 from the > >>> 1.5.0 > >>> > scope. > >>> > > >>> > Robert > >>> > > >>> > > >>> > On Wed, May 6, 2026 at 11:34 AM Jean-Baptiste Onofré < > [email protected]> > >>> > wrote: > >>> > > >>> > > Hi Alex > >>> > > > >>> > > That's a good point. Honestly, as we plan Polaris 1.5.0 next week, > I > >>> > would > >>> > > suggest to consider Iceberg 1.11.0 for Polaris 1.6.0 (mi June). > >>> > > > >>> > > Regards > >>> > > JB > >>> > > > >>> > > On Wed, May 6, 2026 at 8:13 AM Alexandre Dutra <[email protected]> > >>> > wrote: > >>> > > > >>> > > > Hi all, > >>> > > > > >>> > > > If 1.5.0 includes Iceberg 1.11, let’s not forget to incorporate > the > >>> > > changes > >>> > > > already merged in the feature/iceberg-1.11 branch. There also > >>> might be > >>> > > one > >>> > > > or two PRs against that branch that could now be merged (I’m AFK > >>> at the > >>> > > > moment). > >>> > > > > >>> > > > Thanks, > >>> > > > Alex > >>> > > > > >>> > > > Le mer. 6 mai 2026 à 07:10, Jean-Baptiste Onofré < > [email protected]> > >>> a > >>> > > > écrit : > >>> > > > > >>> > > > > Thanks a good point but I would say let's go best effort: if we > >>> can > >>> > > > > integrate Iceberg 1.11.0 for Polaris 1.5.0, we will do that, > but > >>> we > >>> > > > should > >>> > > > > not wait. > >>> > > > > If it's not in Polaris 1.5.0, Iceberg 1.11.0 can be integrated > in > >>> > > Polaris > >>> > > > > 1.6.0 (in June). > >>> > > > > > >>> > > > > Regards > >>> > > > > JB > >>> > > > > > >>> > > > > On Tue, May 5, 2026 at 6:40 PM Ajantha Bhat < > >>> [email protected]> > >>> > > > wrote: > >>> > > > > > >>> > > > > > Hi JB, > >>> > > > > > > >>> > > > > > It looks like we’re very close to the Iceberg 1.11.0 release > >>> based > >>> > on > >>> > > > > this > >>> > > > > > thread < > >>> > > > https://lists.apache.org/thread/z6krfw87qft21rt7nfrdh09qg2h03ryf > >>> > > > > >. > >>> > > > > > I’d suggest waiting for it to be included in the 1.5.0 > release, > >>> > which > >>> > > > > > aligns with our timeline. > >>> > > > > > > >>> > > > > > - Ajantha > >>> > > > > > > >>> > > > > > > >>> > > > > > On Tue, May 5, 2026 at 9:14 PM Dmitri Bourlatchkov < > >>> > [email protected] > >>> > > > > >>> > > > > > wrote: > >>> > > > > > > >>> > > > > > > Hi JB, > >>> > > > > > > > >>> > > > > > > Good idea! > >>> > > > > > > > >>> > > > > > > Cheers, > >>> > > > > > > Dmitri. > >>> > > > > > > > >>> > > > > > > On Tue, May 5, 2026 at 11:37 AM Jean-Baptiste Onofré < > >>> > > > [email protected]> > >>> > > > > > > wrote: > >>> > > > > > > > >>> > > > > > > > Hi everyone, > >>> > > > > > > > > >>> > > > > > > > As we discussed a few weeks ago, I propose releasing > >>> Polaris > >>> > > 1.5.0 > >>> > > > > next > >>> > > > > > > > week to maintain our monthly release cadence. > >>> > > > > > > > > >>> > > > > > > > We currently have nine open issues for this milestone: > >>> > > > > > > > > >>> > > > > > > > > >>> > > > > > > > >>> > > > > > > >>> > > > > > >>> > > > > >>> > > > >>> > > >>> > https://github.com/apache/polaris/issues?q=is%3Aissue%20state%3Aopen%20milestone%3A1.5.0 > >>> > > > > > > > > >>> > > > > > > > I am starting with issue #4367 ( > >>> > > > > > > > https://github.com/apache/polaris/issues/4367) to verify > >>> all > >>> > > legal > >>> > > > > > > aspects > >>> > > > > > > > before the release. > >>> > > > > > > > > >>> > > > > > > > Please update any issues or PRs you would like to include > >>> in > >>> > > > 1.5.0. I > >>> > > > > > > plan > >>> > > > > > > > to begin the release preparation on May 15 if no > >>> objections. > >>> > > > > > > > > >>> > > > > > > > Thoughts? > >>> > > > > > > > > >>> > > > > > > > Regards, > >>> > > > > > > > JB > >>> > > > > > > > > >>> > > > > > > > >>> > > > > > > >>> > > > > > >>> > > > > >>> > > > >>> > > >>> > >> >
