Thanks Dmitri I will review the PRs.
In the meantime, I will start another PR with release blog (highlights/release note). Regards JB On Mon, Aug 25, 2025 at 1:59 AM Dmitri Bourlatchkov <di...@apache.org> wrote: > > Hi Dennis, > > I opened PR [2442] to fix [2436]. > > Please review. > > [2436] https://github.com/apache/polaris/issues/2436 > [2442] https://github.com/apache/polaris/pull/2442 > > Cheers, > Dmitri. > > On Sat, Aug 23, 2025 at 12:42 AM Dmitri Bourlatchkov <di...@apache.org> > wrote: > > > Hi Dennis, > > > > I agree that [2436] is a valid concern and it's worth addressing before > > 1.1.0. > > > > Thanks for catching it. > > > > [2436] https://github.com/apache/polaris/issues/2436 > > > > Cheers, > > Dmitri. > > > > On Fri, Aug 22, 2025 at 11:37 PM Dennis Huo <huoi...@gmail.com> wrote: > > > >> Filed https://github.com/apache/polaris/issues/2436 as a 1.1 blocker, to > >> request a FeatureConfiguration that gates the usage of custom s3/sts > >> endpoints (apologies if I missed an existing FeatureConfiguration flag > >> that > >> otherwise already allows service owners to provide consent or non-consent > >> to Catalog users specifying custom endpoints). > >> > >> If this is a duplicate or already fixed please feel free to close it as > >> such; I just wanted to make sure it's tracked earlier rather than later in > >> case we don't have a gate yet, and a cursory search over > >> FeatureConfiguration didn't show any obvious feature gates. > >> > >> On Fri, Aug 22, 2025 at 1:43 PM Prashant Singh > >> <prashant.si...@snowflake.com.invalid> wrote: > >> > >> > +1 from my end, on adding 2341 on the milestone of 1.1.0 there a couple > >> > users in the iceberg slack for polaris too who are looking forward to > >> this > >> > feature > >> > > >> > On Fri, Aug 22, 2025 at 1:14 PM Dmitri Bourlatchkov <di...@apache.org> > >> > wrote: > >> > > >> > > Hi All, > >> > > > >> > > I see a user-reported issue in slack [1], which I believe is fixed by > >> > > [2341]. > >> > > > >> > > I propose to include [2341] into 1.1.0. The PR is almost ready. I > >> > > proactively added it to the 1.1.0 milestone. > >> > > > >> > > WDYT? > >> > > > >> > > [1] > >> > > > >> > > > >> > > >> https://apache-polaris.slack.com/archives/C084QSKD6S2/p1755892664049749?thread_ts=1755796733.378569&cid=C084QSKD6S2 > >> > > [2341] https://github.com/apache/polaris/pull/2341 > >> > > > >> > > Thanks, > >> > > Dmitri. > >> > > > >> > > On Thu, Aug 21, 2025 at 8:13 PM Prashant Singh < > >> prashant010...@gmail.com > >> > > > >> > > wrote: > >> > > > >> > > > Hey All, > >> > > > I would also request to consider getting credentials vending PR in, > >> > > mostly > >> > > > because a lot of users have raised this issue, for long running jobs > >> > and > >> > > > are eagerly waiting for it ! > >> > > > > >> > > > Best, > >> > > > Prashant Singh > >> > > > > >> > > > > >> > > > On Thu, Aug 21, 2025 at 4:53 PM Dmitri Bourlatchkov < > >> di...@apache.org> > >> > > > wrote: > >> > > > > >> > > > > Hi All, > >> > > > > > >> > > > > Just heads up: it looks like credential refresh config [2341] is > >> > almost > >> > > > > ready. I'm not advocating to hold 1.1.0 for it, but in case it is > >> > > merged > >> > > > in > >> > > > > time, it would be good to mention it in release notes. > >> > > > > > >> > > > > [2341] https://github.com/apache/polaris/pull/2341 > >> > > > > > >> > > > > Cheers, > >> > > > > Dmitri. > >> > > > > > >> > > > > On Tue, Aug 19, 2025 at 3:28 PM Jean-Baptiste Onofré < > >> > j...@nanthrax.net> > >> > > > > wrote: > >> > > > > > >> > > > > > Hi folks, > >> > > > > > > >> > > > > > We currently have 18 issues on the 1.1.0 milestone: > >> > > > > > > >> > > > > > > >> > > > > > >> > > > > >> > > > >> > > >> https://github.com/apache/polaris/issues?q=is%3Aissue%20state%3Aopen%20milestone%3A1.1.0 > >> > > > > > > >> > > > > > As we are now starting to have monthly releases, I propose to > >> bump > >> > > > > > these GH issues with improvements and proposal labels to the > >> 1.2.0 > >> > > > > > milestone (1.2.0-incubating is planned for September). > >> > > > > > Any objections? > >> > > > > > > >> > > > > > For the issues with the "bug" label, I don't see anything major > >> > but I > >> > > > > > would like to give a day for the community to take a look. > >> > > > > > Can you please take a look at the GH issues with the 1.1.0 > >> > milestone > >> > > > > > to bump to 1.2.0 (or later) ? > >> > > > > > Note that we can always include issues for 1.2.0 (September), > >> 1.3.0 > >> > > > > > (October), etc. We basically ship what we have :) > >> > > > > > > >> > > > > > I will do a new pass tomorrow. I would like to start the 1.1.0 > >> > > release > >> > > > > > process by the end of this week. > >> > > > > > > >> > > > > > Thanks ! > >> > > > > > > >> > > > > > Regards > >> > > > > > JB > >> > > > > > > >> > > > > > >> > > > > >> > > > >> > > >> > >
