Hi all, I've worked with JB to verify that we should be ready to cut the release branch for 1.4.0. As we are well past the original branch cut date, I will cut the branch sometime tomorrow, March 4th, 2026 during PST business hours. If you have any last-minute changes that need to go into the 1.4.0 release, please ensure they are merged tonight.
Best, Adnan Hemani On Mon, Feb 23, 2026 at 6:04 AM Jean-Baptiste Onofré <[email protected]> wrote: > Hi > > During the weekend, I reviewed the 1.4.0 release prep. I also found that > LICENSE and NOTICE are not up to date: > - the versions are not up to date (I created a PR to remove the versions ( > https://github.com/apache/polaris/pull/3861 that has been reused by Robert > in the "generation" PR). > - the runtime distributions dependencies changed, but LICENSE/NOTICE have > not been updated (I was about to create another PR about that). > > I mentioned that last week during the Polaris Community Meeting: this is a > blocker for the 1.4.0 release. > > Thanks Robert for the PR, I will review it and double check if we are good > (from a legal standpoint). > > Regards > JB > > On Mon, Feb 23, 2026 at 2:44 PM Robert Stupp <[email protected]> wrote: > > > Hi all, > > > > I reviewed the licenses for the binary distribution, which is part of > > the release management. > > Several changes must be made to the LICENSE files and block the release. > > > > Looking into those, it became apparent that other dependency changes are > > required for version 1.4.0 release. > > > > I have created the relevant PRs and added them to the milestone for the > > 1.4.0 release. > > > > Robert > > > > > > On Tue, Feb 17, 2026 at 2:02 AM Adnan Hemani via dev < > > [email protected]> > > wrote: > > > > > Hi, > > > > > > Thanks for this update - I had it on my calendar today to send out an > > email > > > today to get this started and completely missed this thread in my inbox > > for > > > some reason. > > > > > > Let me start the thread with my initial thoughts on all the remaining > > open > > > issues and PRs later today and we can go from there. > > > > > > Best, > > > Adnan Hemani > > > > > > On Thu, Feb 12, 2026 at 6:58 AM Jean-Baptiste Onofré <[email protected]> > > > wrote: > > > > > > > Hi folks, > > > > > > > > I believe we are approaching the scheduled time for the next release, > > > > following our monthly cadence. > > > > > > > > I just reviewed the GitHub milestone ( > > > > https://github.com/apache/polaris/milestone/6) and noticed there are > > > still > > > > 14 open issues. While some appear close to completion, others may > > require > > > > further discussion. > > > > > > > > Could we perform a triage to determine if these issues should remain > in > > > the > > > > 1.4.0 milestone or be bumped to a later one? > > > > > > > > Adnan, as the release manager, would you mind taking the lead on the > > > > 1.4.0-incubating release preparation? > > > > > > > > Thanks! > > > > Regards, > > > > JB > > > > > > > > On Fri, Jan 30, 2026 at 8:42 PM Jean-Baptiste Onofré < > [email protected]> > > > > wrote: > > > > > > > > > Hi folks > > > > > > > > > > I would like to start a discussion to prepare 1.4.0-incubating. > > > > > > > > > > Who would like to be release manager on this one ? > > > > > > > > > > I will check the milestone on GH. Please assign the 1.4.0 milestone > > to > > > > > issues/PRs you want to include in this release. > > > > > > > > > > Thanks ! > > > > > > > > > > Regards > > > > > JB > > > > > > > > > > > > > > >
