Hi Quick update about Polaris 1.9.0 release.
We still have the PR about Directories Spec open with milestone 1.9.0: https://github.com/apache/polaris/pull/5927 I addressed all comments, so I think it's good to go. Can you please take a look? As soon as this PR is merged, I will cut 1.9.0 RC0. Thanks! Regards JB On Mon, Nov 2, 2026 at 4:24 PM Dmitri Bourlatchkov via dev < [email protected]> wrote: > Hi JB, > > Sorry for the last minute scope creep, but I think PR [5246] is also worth > including into 1.9.0, as discussed on the dedicated dev thread [1]. I > proactively added the 1.9.0 milestone mark to the PR. > > If it takes too long to merge, we can still drop it from 1.9.0, however > that will defer user adoption by another release cycle. Please feel free to > decide on this at your discretion as a release manager. > > [1] https://lists.apache.org/thread/74c9lomv5s59dgts8hzjhzwfyovz9sw9 > > [5246] https://github.com/apache/polaris/pull/5246 > > Thanks, > Dmitri. > > On Tue, Oct 27, 2026 at 1:36 AM Jean-Baptiste Onofré <[email protected]> > wrote: > > > Hi > > > > Yeah, I agree to include #5856 and #5263 in 1.9.0. > > > > I still would like to include the first round of Directories (beta). I > > updated the PR accordingly. Thanks for your help on that :) > > > > Regards > > JB > > > > On Tue, Oct 27, 2026 at 1:20 AM Dmitri Bourlatchkov <[email protected]> > > wrote: > > > > > Hi JB, > > > > > > I think [5856] is worth including into 1.9.0. I added it to the > > milestone. > > > > > > The PR is good to merge from my POV... perhaps with a couple of minor > > > CHANGELOG changes. > > > > > > [5856] https://github.com/apache/polaris/pull/5856 > > > > > > Cheers, > > > Dmitri. > > > > > > On Sun, Oct 25, 2026 at 5:21 AM Jean-Baptiste Onofré <[email protected]> > > > wrote: > > > > > > > Hi everyone, > > > > > > > > I'm starting the triage for the 1.9.0 release. I would like to submit > > > this > > > > release to vote by end of next week (before Halloween :)). > > > > > > > > Regards > > > > JB > > > > > > > > On Tue, Oct 6, 2026 at 10:47 AM Jean-Baptiste Onofré < > [email protected]> > > > > wrote: > > > > > > > > > FYI https://github.com/apache/polaris/pull/5713 > > > > > > > > > > On Tue, Oct 6, 2026 at 10:33 AM Jean-Baptiste Onofré < > > [email protected]> > > > > > wrote: > > > > > > > > > > > > Hi > > > > > > > > > > > > The DOAP is good to keep updated but it's not strictly required. > > > > > > > > > > > > ATR is a different story, as Polaris doesn't use ATR for now. > > > > > > > > > > > > I will add a note in the release guide about DOAP (I'm sure it > was > > > > > > updated in the past, I remember I did it). > > > > > > Some projects decide to not update DOAP file about release at > all. > > > > > > > > > > > > Regards > > > > > > JB > > > > > > > > > > > > On Mon, Oct 5, 2026 at 9:19 PM Ayush Saxena <[email protected]> > > > > wrote: > > > > > > > > > > > > > > Hi Yufei, > > > > > > > The Apache Community Development team maintains this website > [1], > > > and > > > > > > > it sources the project information from the DOAP file, which I > > was > > > > > > > mentioned is the source of information for various lists. > > > > > > > > > > > > > > I double-checked with the ComDev team today, and they also > > > mentioned: > > > > > > > ``` > > > > > > > ATR will consume the DOAP as an option for project definition. > > With > > > > > > > ATR you get all release information from > > > release-catalog.apache.org. > > > > > > > We are also working on PURLs. > > > > > > > ``` > > > > > > > > > > > > > > It should essentially be just one line per release, so, I > thought > > > it > > > > > > > would be good if we can have that updated as part of our > release > > > > > > > process as well :-) > > > > > > > > > > > > > > -Ayush > > > > > > > > > > > > > > [1] https://projects.apache.org/project.html?polaris > > > > > > > > > > > > > > On Tue, 6 Oct 2026 at 00:29, Dmitri Bourlatchkov < > > [email protected] > > > > > > > > > wrote: > > > > > > > > > > > > > > > > Hi JB, > > > > > > > > > > > > > > > > +1 to monthly releases (specifically end of Oct time line). > > > Thanks > > > > > for > > > > > > > > driving the release again! > > > > > > > > > > > > > > > > I have some concerns about LICENSE / NOTICE. Sol/xhigh > > apparently > > > > > finds an > > > > > > > > issue there in my env... It's not a big deal, I think, but > I'd > > > like > > > > > to sort > > > > > > > > it out just to be able to use AI tools for release > validation. > > > I'll > > > > > post > > > > > > > > separately about that... probably as a PR. > > > > > > > > > > > > > > > > In terms of features, it would be nice to get R2 support > merged > > > (as > > > > > "beta", > > > > > > > > of course), but it's not "my" feature... just advocating for > > > Austen > > > > > [1]. > > > > > > > > The fist PR is ready merge: [5513]. I hope subsequent PRs > > should > > > be > > > > > easy > > > > > > > > because I expect them to affect only opt-in logic (from the > > > user's > > > > > POV). > > > > > > > > > > > > > > > > [1] > > > > https://lists.apache.org/thread/ntbo1m33gf2fwdopk7rj25sy9jhx3vvv > > > > > > > > > > > > > > > > [5513] https://github.com/apache/polaris/pull/5513 > > > > > > > > > > > > > > > > Chears, > > > > > > > > Dmitri. > > > > > > > > > > > > > > > > On Mon, Oct 5, 2026 at 1:36 AM Jean-Baptiste Onofré < > > > > [email protected]> > > > > > wrote: > > > > > > > > > > > > > > > > > Hi folks, > > > > > > > > > > > > > > > > > > In our purpose of monthly release cadence, I would like to > > > > propose > > > > > to > > > > > > > > > release Polaris 1.9.0 by the end of October. > > > > > > > > > I'm volunteer to drive this release. > > > > > > > > > > > > > > > > > > In term of release scope, I would like (as best effort) to > > > > > consider Polaris > > > > > > > > > Directory (with beta flag). I updated the PR (adding a > simple > > > > scan > > > > > service > > > > > > > > > and supporting external services/delegation services, > etc). I > > > > will > > > > > do a new > > > > > > > > > pass on the PR (moving to ready to review) but you can > > already > > > > > chime in > > > > > > > > > there. > > > > > > > > > > > > > > > > > > I will create the milestone on GitHub and we can already > > start > > > > the > > > > > triage. > > > > > > > > > > > > > > > > > > Thoughts? > > > > > > > > > > > > > > > > > > Regards > > > > > > > > > JB > > > > > > > > > > > > > > > > > > > > > > > >
