Hi Adnand and All, Thanks for driving the release discussion!
* [CLOSE] #552 <https://github.com/apache/polaris/issues/552>: Safety against unparseable locations. * I believe all the work has been completed for this. Dmitri, can you please confirm? (Will follow up offline as well) I do not think 552 should be closed. I'm pretty sure there are still cases where storage locations that do not match the URI syntax may cause runtime errors. However, I'm fine with removing it from the 1.4.0 milestone. If users hit related problems in practice, we can accelerate fixing it. In general, it may not affect real word scenarios that much, but we should keep it in the backlog as a reminder to achieve total correctness in location string handling. * [DISCUSS] #650 <https://github.com/apache/polaris/issues/650> / #3395 <https://github.com/apache/polaris/pull/3395>: MongoDB Persistence Backend As far as I understand, [3395] is the only remaining PR before 650 can be claimed "done". [3395], indeed, is under discussion [1] WRT to whether to put the new maintenance command into the Admin Tool or have another solution. If we are ok with putting it in the Admin Tool, PR [3395] is ready to merge right away and we can complete 650 for 1.4.0. Otherwise, I believe we have to push both [3395] and 650 out of 1.4.0. Given previous discussions on [1], my understanding is that we're close to consensus on putting NoSQL maintenance into the Admin tool for now and discussing follow-up work on `main`. Therefore, I propose to merge [3395] now. I wonder what Yufei's opinion on this is. [1] https://lists.apache.org/thread/yf7nmx0sq87wzbxtjsz32cj1069jcfll [3395] https://github.com/apache/polaris/pull/3395 Thanks, Dmitri. On Tue, Feb 17, 2026 at 12:15 AM Jean-Baptiste Onofré <[email protected]> wrote: > Hi Adnan > > Thanks for starting the thread. > > Regarding the timing, I propose to bump all pending PR to 1.5.0 release. As > part of our "release pace", we focus on monthly release and I don't see any > strong PR that would need to delay the release. > > Thanks again! > Regards > JB > > On Tue, Feb 17, 2026 at 3:37 AM Adnan Hemani via dev < > [email protected]> > wrote: > > > Hi all, > > > > I've gone through the GH issues and PRs tagged to the 1.4.0 label and > would > > like to make the following recommendations for a potential Apache Polaris > > 1.4.0 release branch cut on (tentatively) 2026-02-23. > > > > Please reply to this thread prior to that date if there is any feedback, > > comments, and/or concerns so that we can get community consensus before > we > > proceed with the release. If there are no replies to this email, the > 1.4.0 > > release branch will be cut on 2026-02-23. > > > > Open Issues (Recommendation in []): > > * [PUNT] #538 <https://github.com/apache/polaris/issues/538>: Table > > Maintenance Support in Polaris > > * No major work in progress to justify delaying the release. > > > > * [CLOSE] #550 <https://github.com/apache/polaris/issues/550>: Support > for > > GCP service account impersonation. > > * I will ping Michael to do this when he is back from vacation. > > > > * [CLOSE] #552 <https://github.com/apache/polaris/issues/552>: Safety > > against unparseable locations. > > * I believe all the work has been completed for this. Dmitri, can you > > please confirm? (Will follow up offline as well) > > > > * [DISCUSS] #650 <https://github.com/apache/polaris/issues/650> / #3395 > > <https://github.com/apache/polaris/pull/3395>: MongoDB Persistence > Backend > > * It seems that discussions are still active and ongoing, and there > is > > disagreement behind getting the change into Admin Tools while the core > > functionality is merged already. I can see the arguments from both sides > to > > push 1.4.0 without the Admin Tools change OR to hold the release until > > there is agreement on these last bit of changes. What are the community's > > thoughts? Default option (if no one chimes in): we will push the release > > as-is on the 23rd. > > > > * [PUNT] #2671 <https://github.com/apache/polaris/issues/2671>: DB > Schema > > Migration Between Releases > > * No major work in progress to justify delaying the release. > > > > * [PUNT] #3685 <https://github.com/apache/polaris/issues/3685>: > > `Create_Namespace` SQL Optimization > > * While there is traction, we may still be too far from a load-tested > > fix. This should be a high priority for 1.5.0. > > > > Open PRs: > > > > * [PUNT] #2180 <https://github.com/apache/polaris/pull/2180>: Async & > > reliable tasks API, SPI, Store interfaces > > * PR is not very active over the last few weeks and does not have > > enough active reviewers to see a strong path forward for merging in the > > next week or so. > > > > * [PUNT] #3256 <https://github.com/apache/polaris/pull/3256>: Object > > Storage Operations > > * From the ML, it seems that there are still two rival proposals that > > are attempting to solve similar issues. My recommendation is to unstick > > this discussion from the 1.4.0 release to give proper time for the > > discussion to resolve. > > > > When commenting, please reference the GH Issue/PR number so that we are > > clear on what is being discussed :) > > > > Best, > > Adnan Hemani > > >
