Thanks for the summary, JB!

I do believe [608] is no longer an issue, but I'm not 100% sure. If nobody
has time to re-test it, it should be fine to defer testing it until after
1.1.0.

[608] https://github.com/apache/polaris/issues/608

Cheers,
Dmitri.

On Fri, Aug 22, 2025 at 12:44 AM Jean-Baptiste Onofré <j...@nanthrax.net>
wrote:

> Hi folks,
>
> I did a triage on the GH issue with the 1.1.0 milestone.
>
> Only one issue is pending, but I think it's fixed:
> https://github.com/apache/polaris/issues/608
> I will test it today but if someone has an update, that would be helpful.
>
> Regarding the PRs with the 1.1.0 milestone:
> * https://github.com/apache/polaris/pull/1424 has a few conflicts to
> be solved and still has comments. I propose to update the PR with the
> 1.2.0 milestone and aim the 1.2.0 release (September).
> * as it's a proposal and initial draft, I updated
> https://github.com/apache/polaris/pull/1439 to the 1.2.0 milestone. As
> it's related, also https://github.com/apache/polaris/pull/1862 has
> been "moved" to the 1.2.0 milestone.
> * I reviewed https://github.com/apache/polaris/pull/2404 and it looks
> good to me. So this PR will be merged today (with the 1.1.0 milestone
> target).
>
> I'm doing a pass on LICENSE/NOTICE/DISCLAIMER, etc. I would like to
> start the 1.1.0 release prep tonight or during the weekend.
>
> Thanks !
>
> Regards
> JB
>
> On Fri, Aug 22, 2025 at 1:51 AM 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
> > >
>

Reply via email to