You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@polaris.apache.org by Prashant Singh <pr...@snowflake.com.INVALID> on 2025/09/15 20:46:02 UTC
DISCUSS: 1.2 release
Hey All,
Thank you everyone for working on the 1.1 release now since it is *almost*
done and we planned on a monthly release cadence, I was wondering if we
should start thinking of a 1.2 release and start working towards
identifying what we want to target for 1.2.
Given that I would also like to volunteer as 1.2 release manager, please
let me know your thoughts !
Best,
Prashant Singh
Re: DISCUSS: 1.2 release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Prashant
I'm doing a check on the "legal" (LICENSE, NOTICE, etc in the packages).
I will eventually open PRs.
I will keep you posted.
Regards
JB
On Tue, Oct 7, 2025 at 8:34 AM Prashant Singh
<pr...@snowflake.com.invalid> wrote:
>
> Thank you everyone for your awesome work, I wanted to share that all the
> 1.2 critical fixes are in !
> At this point the window for including more changes 1.2 is closed (obvious
> if anything critical comes up, we should definitely discuss and make a call
> on it together).
> I will start prepping the RC for the release and share it when ready.
>
> Again thanks a ton to everyone !
>
> Best,
> Prashant Singh
>
>
>
> On Fri, Sep 26, 2025 at 5:05 PM Honah J. <ho...@apache.org> wrote:
>
> > Hi Prashant,
> >
> > Yes, that sounds great! The remaining task is mostly to finalize a proper
> > release process for python CLI. But if we discover something more later, it
> > definitely makes sense to target the next.
> >
> > Best,
> > Jonas
> >
> > On Fri, Sep 26, 2025 at 6:58 PM Prashant Singh
> > <pr...@snowflake.com.invalid> wrote:
> >
> > > Hey Jonas,
> > > Thank you for bringing this up, i think we are still waiting on some of
> > the
> > > fixes which are required for 1.2
> > > if its gets in by the time these get resolved, happy to include this in
> > > 1.2, though if its gonna take some more time or requires some further
> > > discussion,
> > > imho then we can wait for it 1.3 which would just next end of october,
> > WDYT
> > > ?
> > >
> > > Best,
> > > Prashant Singh
> > >
> > > On Fri, Sep 26, 2025 at 1:28 PM Honah J. <ho...@apache.org> wrote:
> > >
> > > > Hi Prashant,
> > > >
> > > > Thanks for driving this! Sorry for the lateness that I did not realize
> > > > that Python CLI binary distribution [2419] is not currently tracked in
> > > > milestone 1.2.0. The goal is to make it easier for users to use our CLI
> > > to
> > > > interact with polaris (with simple pip install instead of cloning the
> > > whole
> > > > project). There has been much progress from Yong and Yufei and I think
> > we
> > > > are close. WDYT about including this to 1.2.0 milestone?
> > > >
> > > > [2419]: https://github.com/apache/polaris/issues/2419
> > > > <https://github.com/apache/polaris/issues/2419>
> > > >
> > > > Thanks!
> > > > Jonas
> > > >
> > > > On Fri, Sep 26, 2025 at 2:28 PM Dmitri Bourlatchkov <di...@apache.org>
> > > > wrote:
> > > >
> > > > > Hi Prashant,
> > > > >
> > > > > I've also marked [2696] for 1.2.0. The reason is that it's a
> > follow-up
> > > PR
> > > > > to something that got recently merged to `main` and we need to
> > resolve
> > > it
> > > > > to avoid possible inconvenience (as discussed in the PRs).
> > > > >
> > > > > [2696] https://github.com/apache/polaris/pull/2696
> > > > >
> > > > > Cheers,
> > > > > Dmitri.
> > > > >
> > > > > On Fri, Sep 26, 2025 at 12:40 PM Prashant Singh
> > > > > <pr...@snowflake.com.invalid> wrote:
> > > > >
> > > > > > Thank you everyone ! for you inputs
> > > > > > I see all PRs from Alex marked for 1.2 is merged, and as per
> > > feedback i
> > > > > > moved issues / features marked for 1.2 to either 1.3 or simply
> > > removed
> > > > > > milestones for the features we haven't started
> > > > > > developing on.
> > > > > > My current understanding is that we are waiting for :
> > > > > > [1] PR - https://github.com/apache/polaris/pull/2653
> > > > > > [2] Issue - https://github.com/apache/polaris/issues/2671 so that
> > > > > rolling
> > > > > > upgrades are handled correctly (we have a thread for this already)
> > > > > >
> > > > > > If this understanding is correct, then post resolution of [1] and
> > [2]
> > > > we
> > > > > > should be good to move forward with 1.2 rc cut.
> > > > > > Please let me know if I am missing anything, if all are ok i will
> > > track
> > > > > > these 2 to move forward with 1.2 rc cut to continue our monthly
> > > release
> > > > > > train model.
> > > > > >
> > > > > > Best,
> > > > > > Prashant Singh
> > > > > >
> > > > > > On Tue, Sep 16, 2025 at 1:58 PM Prashant Singh <
> > > > > > prashant.singh@snowflake.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Thank you JB & Alex !
> > > > > > >
> > > > > > > Re: semi automatic effort, I propose also to move forward on the
> > GH
> > > > > > > Release Action
> > > > > > > if the GH Release Action is ready and happy to give it a spin !
> > > > > > >
> > > > > > > Re: I have proactively assigned the 1.2.0 milestone to some of my
> > > PRs
> > > > > > that
> > > > > > > I think could be part of 1.2.0.
> > > > > > > Thank you Alex for also starting the thread for this ! I hope
> > these
> > > > get
> > > > > > in
> > > > > > > soon :) !
> > > > > > >
> > > > > > > Re: What do we want to do with remote signing?
> > > > > > > I am not sure of next steps here, how about we see if we can get
> > in
> > > > by
> > > > > > the
> > > > > > > rc cutoff to catch 1.2 train.
> > > > > > >
> > > > > > > Again thank you everyone for your feedbacks looking forward to
> > 1.2
> > > > > > release
> > > > > > >
> > > > > > > I also added an iceberg version bump to 1.10 in this track, as
> > our
> > > > > tests
> > > > > > > were failing with dependabot update, it will be nice to include
> > > this
> > > > as
> > > > > > > well !
> > > > > > > https://github.com/apache/polaris/pull/2586
> > > > > > >
> > > > > > > Best,
> > > > > > > Prashant Singh
> > > > > > >
> > > > > > >
> > > > > > > On Tue, Sep 16, 2025 at 9:53 AM Alexandre Dutra <
> > adutra@apache.org
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > >> Hi Prashant, hi all,
> > > > > > >>
> > > > > > >> Thanks for driving the 1.2 release effort!
> > > > > > >>
> > > > > > >> I have proactively assigned the 1.2.0 milestone to some of my
> > PRs
> > > > that
> > > > > > >> I think could be part of 1.2.0.
> > > > > > >>
> > > > > > >> What do we want to do with remote signing? I think we could
> > > include
> > > > > > >> the current PR in experimental / preview state, but I'm fine
> > > holding
> > > > > > >> off until we finish the implementation if you think that's
> > safer.
> > > > > > >>
> > > > > > >> Thanks,
> > > > > > >> Alex
> > > > > > >>
> > > > > > >> On Tue, Sep 16, 2025 at 8:06 AM Jean-Baptiste Onofré <
> > > > jb@nanthrax.net
> > > > > >
> > > > > > >> wrote:
> > > > > > >> >
> > > > > > >> > Hi
> > > > > > >> >
> > > > > > >> > Thanks for starting this ! It makes to me.
> > > > > > >> >
> > > > > > >> > And yes, it makes sense to start the prep/triage now.
> > > > > > >> >
> > > > > > >> > As part of semi auromatic effort, I propose also to move
> > forward
> > > > on
> > > > > > the
> > > > > > >> GH
> > > > > > >> > Release Action.
> > > > > > >> >
> > > > > > >> > Regards
> > > > > > >> > JB
> > > > > > >> >
> > > > > > >> > Le mar. 16 sept. 2025 à 02:16, Prashant Singh
> > > > > > >> > <pr...@snowflake.com.invalid> a écrit :
> > > > > > >> >
> > > > > > >> > > Ack ! Thank you for the feedback Dmitri !
> > > > > > >> > > Tracking 1.2 milestones
> > > > > > >> > > <
> > > > > > >> > >
> > > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> > https://github.com/apache/polaris/issues?q=is%3Aissue%20state%3Aopen%20milestone%3A1.2.0
> > > > > > >> > > >
> > > > > > >> > > for the release (will check the current status of the
> > tickets
> > > /
> > > > > prs
> > > > > > >> already
> > > > > > >> > > tagged with the 1.2 release and check with all) seems
> > > reasonable
> > > > > to
> > > > > > >> me !
> > > > > > >> > >
> > > > > > >> > > Best,
> > > > > > >> > > Prashant Singh
> > > > > > >> > >
> > > > > > >> > > On Mon, Sep 15, 2025 at 2:42 PM Dmitri Bourlatchkov <
> > > > > > dimas@apache.org
> > > > > > >> >
> > > > > > >> > > wrote:
> > > > > > >> > >
> > > > > > >> > > > Thanks for volunteering to drive the 1.2 release,
> > Prashant!
> > > > > > >> > > >
> > > > > > >> > > > I believe we previously discussed using the "release
> > train"
> > > > > model,
> > > > > > >> so
> > > > > > >> > > > whatever is committed by the branch time, gets released :)
> > > > > > >> > > >
> > > > > > >> > > > I propose to use the 1.2.0 GH milestone for tracking PRs
> > and
> > > > > > Issues
> > > > > > >> that
> > > > > > >> > > > need special attention during the 1.2 release (e.g.
> > > blockers).
> > > > > > >> > > >
> > > > > > >> > > > I believe this process worked fairly well for the 1.1.0
> > > > release
> > > > > :)
> > > > > > >> > > >
> > > > > > >> > > > Cheers,
> > > > > > >> > > > Dmitri.
> > > > > > >> > > >
> > > > > > >> > > > On Mon, Sep 15, 2025 at 4:48 PM Prashant Singh
> > > > > > >> > > > <pr...@snowflake.com.invalid> wrote:
> > > > > > >> > > >
> > > > > > >> > > > > Hey All,
> > > > > > >> > > > >
> > > > > > >> > > > > Thank you everyone for working on the 1.1 release now
> > > since
> > > > it
> > > > > > is
> > > > > > >> > > > *almost*
> > > > > > >> > > > > done and we planned on a monthly release cadence, I was
> > > > > > wondering
> > > > > > >> if we
> > > > > > >> > > > > should start thinking of a 1.2 release and start working
> > > > > towards
> > > > > > >> > > > > identifying what we want to target for 1.2.
> > > > > > >> > > > >
> > > > > > >> > > > > Given that I would also like to volunteer as 1.2 release
> > > > > > manager,
> > > > > > >> > > please
> > > > > > >> > > > > let me know your thoughts !
> > > > > > >> > > > >
> > > > > > >> > > > > Best,
> > > > > > >> > > > > Prashant Singh
> > > > > > >> > > > >
> > > > > > >> > > >
> > > > > > >> > >
> > > > > > >>
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
Re: DISCUSS: 1.2 release
Posted by Prashant Singh <pr...@snowflake.com.INVALID>.
Thank you everyone for your awesome work, I wanted to share that all the
1.2 critical fixes are in !
At this point the window for including more changes 1.2 is closed (obvious
if anything critical comes up, we should definitely discuss and make a call
on it together).
I will start prepping the RC for the release and share it when ready.
Again thanks a ton to everyone !
Best,
Prashant Singh
On Fri, Sep 26, 2025 at 5:05 PM Honah J. <ho...@apache.org> wrote:
> Hi Prashant,
>
> Yes, that sounds great! The remaining task is mostly to finalize a proper
> release process for python CLI. But if we discover something more later, it
> definitely makes sense to target the next.
>
> Best,
> Jonas
>
> On Fri, Sep 26, 2025 at 6:58 PM Prashant Singh
> <pr...@snowflake.com.invalid> wrote:
>
> > Hey Jonas,
> > Thank you for bringing this up, i think we are still waiting on some of
> the
> > fixes which are required for 1.2
> > if its gets in by the time these get resolved, happy to include this in
> > 1.2, though if its gonna take some more time or requires some further
> > discussion,
> > imho then we can wait for it 1.3 which would just next end of october,
> WDYT
> > ?
> >
> > Best,
> > Prashant Singh
> >
> > On Fri, Sep 26, 2025 at 1:28 PM Honah J. <ho...@apache.org> wrote:
> >
> > > Hi Prashant,
> > >
> > > Thanks for driving this! Sorry for the lateness that I did not realize
> > > that Python CLI binary distribution [2419] is not currently tracked in
> > > milestone 1.2.0. The goal is to make it easier for users to use our CLI
> > to
> > > interact with polaris (with simple pip install instead of cloning the
> > whole
> > > project). There has been much progress from Yong and Yufei and I think
> we
> > > are close. WDYT about including this to 1.2.0 milestone?
> > >
> > > [2419]: https://github.com/apache/polaris/issues/2419
> > > <https://github.com/apache/polaris/issues/2419>
> > >
> > > Thanks!
> > > Jonas
> > >
> > > On Fri, Sep 26, 2025 at 2:28 PM Dmitri Bourlatchkov <di...@apache.org>
> > > wrote:
> > >
> > > > Hi Prashant,
> > > >
> > > > I've also marked [2696] for 1.2.0. The reason is that it's a
> follow-up
> > PR
> > > > to something that got recently merged to `main` and we need to
> resolve
> > it
> > > > to avoid possible inconvenience (as discussed in the PRs).
> > > >
> > > > [2696] https://github.com/apache/polaris/pull/2696
> > > >
> > > > Cheers,
> > > > Dmitri.
> > > >
> > > > On Fri, Sep 26, 2025 at 12:40 PM Prashant Singh
> > > > <pr...@snowflake.com.invalid> wrote:
> > > >
> > > > > Thank you everyone ! for you inputs
> > > > > I see all PRs from Alex marked for 1.2 is merged, and as per
> > feedback i
> > > > > moved issues / features marked for 1.2 to either 1.3 or simply
> > removed
> > > > > milestones for the features we haven't started
> > > > > developing on.
> > > > > My current understanding is that we are waiting for :
> > > > > [1] PR - https://github.com/apache/polaris/pull/2653
> > > > > [2] Issue - https://github.com/apache/polaris/issues/2671 so that
> > > > rolling
> > > > > upgrades are handled correctly (we have a thread for this already)
> > > > >
> > > > > If this understanding is correct, then post resolution of [1] and
> [2]
> > > we
> > > > > should be good to move forward with 1.2 rc cut.
> > > > > Please let me know if I am missing anything, if all are ok i will
> > track
> > > > > these 2 to move forward with 1.2 rc cut to continue our monthly
> > release
> > > > > train model.
> > > > >
> > > > > Best,
> > > > > Prashant Singh
> > > > >
> > > > > On Tue, Sep 16, 2025 at 1:58 PM Prashant Singh <
> > > > > prashant.singh@snowflake.com>
> > > > > wrote:
> > > > >
> > > > > > Thank you JB & Alex !
> > > > > >
> > > > > > Re: semi automatic effort, I propose also to move forward on the
> GH
> > > > > > Release Action
> > > > > > if the GH Release Action is ready and happy to give it a spin !
> > > > > >
> > > > > > Re: I have proactively assigned the 1.2.0 milestone to some of my
> > PRs
> > > > > that
> > > > > > I think could be part of 1.2.0.
> > > > > > Thank you Alex for also starting the thread for this ! I hope
> these
> > > get
> > > > > in
> > > > > > soon :) !
> > > > > >
> > > > > > Re: What do we want to do with remote signing?
> > > > > > I am not sure of next steps here, how about we see if we can get
> in
> > > by
> > > > > the
> > > > > > rc cutoff to catch 1.2 train.
> > > > > >
> > > > > > Again thank you everyone for your feedbacks looking forward to
> 1.2
> > > > > release
> > > > > >
> > > > > > I also added an iceberg version bump to 1.10 in this track, as
> our
> > > > tests
> > > > > > were failing with dependabot update, it will be nice to include
> > this
> > > as
> > > > > > well !
> > > > > > https://github.com/apache/polaris/pull/2586
> > > > > >
> > > > > > Best,
> > > > > > Prashant Singh
> > > > > >
> > > > > >
> > > > > > On Tue, Sep 16, 2025 at 9:53 AM Alexandre Dutra <
> adutra@apache.org
> > >
> > > > > wrote:
> > > > > >
> > > > > >> Hi Prashant, hi all,
> > > > > >>
> > > > > >> Thanks for driving the 1.2 release effort!
> > > > > >>
> > > > > >> I have proactively assigned the 1.2.0 milestone to some of my
> PRs
> > > that
> > > > > >> I think could be part of 1.2.0.
> > > > > >>
> > > > > >> What do we want to do with remote signing? I think we could
> > include
> > > > > >> the current PR in experimental / preview state, but I'm fine
> > holding
> > > > > >> off until we finish the implementation if you think that's
> safer.
> > > > > >>
> > > > > >> Thanks,
> > > > > >> Alex
> > > > > >>
> > > > > >> On Tue, Sep 16, 2025 at 8:06 AM Jean-Baptiste Onofré <
> > > jb@nanthrax.net
> > > > >
> > > > > >> wrote:
> > > > > >> >
> > > > > >> > Hi
> > > > > >> >
> > > > > >> > Thanks for starting this ! It makes to me.
> > > > > >> >
> > > > > >> > And yes, it makes sense to start the prep/triage now.
> > > > > >> >
> > > > > >> > As part of semi auromatic effort, I propose also to move
> forward
> > > on
> > > > > the
> > > > > >> GH
> > > > > >> > Release Action.
> > > > > >> >
> > > > > >> > Regards
> > > > > >> > JB
> > > > > >> >
> > > > > >> > Le mar. 16 sept. 2025 à 02:16, Prashant Singh
> > > > > >> > <pr...@snowflake.com.invalid> a écrit :
> > > > > >> >
> > > > > >> > > Ack ! Thank you for the feedback Dmitri !
> > > > > >> > > Tracking 1.2 milestones
> > > > > >> > > <
> > > > > >> > >
> > > > > >>
> > > > >
> > > >
> > >
> >
> https://github.com/apache/polaris/issues?q=is%3Aissue%20state%3Aopen%20milestone%3A1.2.0
> > > > > >> > > >
> > > > > >> > > for the release (will check the current status of the
> tickets
> > /
> > > > prs
> > > > > >> already
> > > > > >> > > tagged with the 1.2 release and check with all) seems
> > reasonable
> > > > to
> > > > > >> me !
> > > > > >> > >
> > > > > >> > > Best,
> > > > > >> > > Prashant Singh
> > > > > >> > >
> > > > > >> > > On Mon, Sep 15, 2025 at 2:42 PM Dmitri Bourlatchkov <
> > > > > dimas@apache.org
> > > > > >> >
> > > > > >> > > wrote:
> > > > > >> > >
> > > > > >> > > > Thanks for volunteering to drive the 1.2 release,
> Prashant!
> > > > > >> > > >
> > > > > >> > > > I believe we previously discussed using the "release
> train"
> > > > model,
> > > > > >> so
> > > > > >> > > > whatever is committed by the branch time, gets released :)
> > > > > >> > > >
> > > > > >> > > > I propose to use the 1.2.0 GH milestone for tracking PRs
> and
> > > > > Issues
> > > > > >> that
> > > > > >> > > > need special attention during the 1.2 release (e.g.
> > blockers).
> > > > > >> > > >
> > > > > >> > > > I believe this process worked fairly well for the 1.1.0
> > > release
> > > > :)
> > > > > >> > > >
> > > > > >> > > > Cheers,
> > > > > >> > > > Dmitri.
> > > > > >> > > >
> > > > > >> > > > On Mon, Sep 15, 2025 at 4:48 PM Prashant Singh
> > > > > >> > > > <pr...@snowflake.com.invalid> wrote:
> > > > > >> > > >
> > > > > >> > > > > Hey All,
> > > > > >> > > > >
> > > > > >> > > > > Thank you everyone for working on the 1.1 release now
> > since
> > > it
> > > > > is
> > > > > >> > > > *almost*
> > > > > >> > > > > done and we planned on a monthly release cadence, I was
> > > > > wondering
> > > > > >> if we
> > > > > >> > > > > should start thinking of a 1.2 release and start working
> > > > towards
> > > > > >> > > > > identifying what we want to target for 1.2.
> > > > > >> > > > >
> > > > > >> > > > > Given that I would also like to volunteer as 1.2 release
> > > > > manager,
> > > > > >> > > please
> > > > > >> > > > > let me know your thoughts !
> > > > > >> > > > >
> > > > > >> > > > > Best,
> > > > > >> > > > > Prashant Singh
> > > > > >> > > > >
> > > > > >> > > >
> > > > > >> > >
> > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: DISCUSS: 1.2 release
Posted by "Honah J." <ho...@apache.org>.
Hi Prashant,
Yes, that sounds great! The remaining task is mostly to finalize a proper
release process for python CLI. But if we discover something more later, it
definitely makes sense to target the next.
Best,
Jonas
On Fri, Sep 26, 2025 at 6:58 PM Prashant Singh
<pr...@snowflake.com.invalid> wrote:
> Hey Jonas,
> Thank you for bringing this up, i think we are still waiting on some of the
> fixes which are required for 1.2
> if its gets in by the time these get resolved, happy to include this in
> 1.2, though if its gonna take some more time or requires some further
> discussion,
> imho then we can wait for it 1.3 which would just next end of october, WDYT
> ?
>
> Best,
> Prashant Singh
>
> On Fri, Sep 26, 2025 at 1:28 PM Honah J. <ho...@apache.org> wrote:
>
> > Hi Prashant,
> >
> > Thanks for driving this! Sorry for the lateness that I did not realize
> > that Python CLI binary distribution [2419] is not currently tracked in
> > milestone 1.2.0. The goal is to make it easier for users to use our CLI
> to
> > interact with polaris (with simple pip install instead of cloning the
> whole
> > project). There has been much progress from Yong and Yufei and I think we
> > are close. WDYT about including this to 1.2.0 milestone?
> >
> > [2419]: https://github.com/apache/polaris/issues/2419
> > <https://github.com/apache/polaris/issues/2419>
> >
> > Thanks!
> > Jonas
> >
> > On Fri, Sep 26, 2025 at 2:28 PM Dmitri Bourlatchkov <di...@apache.org>
> > wrote:
> >
> > > Hi Prashant,
> > >
> > > I've also marked [2696] for 1.2.0. The reason is that it's a follow-up
> PR
> > > to something that got recently merged to `main` and we need to resolve
> it
> > > to avoid possible inconvenience (as discussed in the PRs).
> > >
> > > [2696] https://github.com/apache/polaris/pull/2696
> > >
> > > Cheers,
> > > Dmitri.
> > >
> > > On Fri, Sep 26, 2025 at 12:40 PM Prashant Singh
> > > <pr...@snowflake.com.invalid> wrote:
> > >
> > > > Thank you everyone ! for you inputs
> > > > I see all PRs from Alex marked for 1.2 is merged, and as per
> feedback i
> > > > moved issues / features marked for 1.2 to either 1.3 or simply
> removed
> > > > milestones for the features we haven't started
> > > > developing on.
> > > > My current understanding is that we are waiting for :
> > > > [1] PR - https://github.com/apache/polaris/pull/2653
> > > > [2] Issue - https://github.com/apache/polaris/issues/2671 so that
> > > rolling
> > > > upgrades are handled correctly (we have a thread for this already)
> > > >
> > > > If this understanding is correct, then post resolution of [1] and [2]
> > we
> > > > should be good to move forward with 1.2 rc cut.
> > > > Please let me know if I am missing anything, if all are ok i will
> track
> > > > these 2 to move forward with 1.2 rc cut to continue our monthly
> release
> > > > train model.
> > > >
> > > > Best,
> > > > Prashant Singh
> > > >
> > > > On Tue, Sep 16, 2025 at 1:58 PM Prashant Singh <
> > > > prashant.singh@snowflake.com>
> > > > wrote:
> > > >
> > > > > Thank you JB & Alex !
> > > > >
> > > > > Re: semi automatic effort, I propose also to move forward on the GH
> > > > > Release Action
> > > > > if the GH Release Action is ready and happy to give it a spin !
> > > > >
> > > > > Re: I have proactively assigned the 1.2.0 milestone to some of my
> PRs
> > > > that
> > > > > I think could be part of 1.2.0.
> > > > > Thank you Alex for also starting the thread for this ! I hope these
> > get
> > > > in
> > > > > soon :) !
> > > > >
> > > > > Re: What do we want to do with remote signing?
> > > > > I am not sure of next steps here, how about we see if we can get in
> > by
> > > > the
> > > > > rc cutoff to catch 1.2 train.
> > > > >
> > > > > Again thank you everyone for your feedbacks looking forward to 1.2
> > > > release
> > > > >
> > > > > I also added an iceberg version bump to 1.10 in this track, as our
> > > tests
> > > > > were failing with dependabot update, it will be nice to include
> this
> > as
> > > > > well !
> > > > > https://github.com/apache/polaris/pull/2586
> > > > >
> > > > > Best,
> > > > > Prashant Singh
> > > > >
> > > > >
> > > > > On Tue, Sep 16, 2025 at 9:53 AM Alexandre Dutra <adutra@apache.org
> >
> > > > wrote:
> > > > >
> > > > >> Hi Prashant, hi all,
> > > > >>
> > > > >> Thanks for driving the 1.2 release effort!
> > > > >>
> > > > >> I have proactively assigned the 1.2.0 milestone to some of my PRs
> > that
> > > > >> I think could be part of 1.2.0.
> > > > >>
> > > > >> What do we want to do with remote signing? I think we could
> include
> > > > >> the current PR in experimental / preview state, but I'm fine
> holding
> > > > >> off until we finish the implementation if you think that's safer.
> > > > >>
> > > > >> Thanks,
> > > > >> Alex
> > > > >>
> > > > >> On Tue, Sep 16, 2025 at 8:06 AM Jean-Baptiste Onofré <
> > jb@nanthrax.net
> > > >
> > > > >> wrote:
> > > > >> >
> > > > >> > Hi
> > > > >> >
> > > > >> > Thanks for starting this ! It makes to me.
> > > > >> >
> > > > >> > And yes, it makes sense to start the prep/triage now.
> > > > >> >
> > > > >> > As part of semi auromatic effort, I propose also to move forward
> > on
> > > > the
> > > > >> GH
> > > > >> > Release Action.
> > > > >> >
> > > > >> > Regards
> > > > >> > JB
> > > > >> >
> > > > >> > Le mar. 16 sept. 2025 à 02:16, Prashant Singh
> > > > >> > <pr...@snowflake.com.invalid> a écrit :
> > > > >> >
> > > > >> > > Ack ! Thank you for the feedback Dmitri !
> > > > >> > > Tracking 1.2 milestones
> > > > >> > > <
> > > > >> > >
> > > > >>
> > > >
> > >
> >
> https://github.com/apache/polaris/issues?q=is%3Aissue%20state%3Aopen%20milestone%3A1.2.0
> > > > >> > > >
> > > > >> > > for the release (will check the current status of the tickets
> /
> > > prs
> > > > >> already
> > > > >> > > tagged with the 1.2 release and check with all) seems
> reasonable
> > > to
> > > > >> me !
> > > > >> > >
> > > > >> > > Best,
> > > > >> > > Prashant Singh
> > > > >> > >
> > > > >> > > On Mon, Sep 15, 2025 at 2:42 PM Dmitri Bourlatchkov <
> > > > dimas@apache.org
> > > > >> >
> > > > >> > > wrote:
> > > > >> > >
> > > > >> > > > Thanks for volunteering to drive the 1.2 release, Prashant!
> > > > >> > > >
> > > > >> > > > I believe we previously discussed using the "release train"
> > > model,
> > > > >> so
> > > > >> > > > whatever is committed by the branch time, gets released :)
> > > > >> > > >
> > > > >> > > > I propose to use the 1.2.0 GH milestone for tracking PRs and
> > > > Issues
> > > > >> that
> > > > >> > > > need special attention during the 1.2 release (e.g.
> blockers).
> > > > >> > > >
> > > > >> > > > I believe this process worked fairly well for the 1.1.0
> > release
> > > :)
> > > > >> > > >
> > > > >> > > > Cheers,
> > > > >> > > > Dmitri.
> > > > >> > > >
> > > > >> > > > On Mon, Sep 15, 2025 at 4:48 PM Prashant Singh
> > > > >> > > > <pr...@snowflake.com.invalid> wrote:
> > > > >> > > >
> > > > >> > > > > Hey All,
> > > > >> > > > >
> > > > >> > > > > Thank you everyone for working on the 1.1 release now
> since
> > it
> > > > is
> > > > >> > > > *almost*
> > > > >> > > > > done and we planned on a monthly release cadence, I was
> > > > wondering
> > > > >> if we
> > > > >> > > > > should start thinking of a 1.2 release and start working
> > > towards
> > > > >> > > > > identifying what we want to target for 1.2.
> > > > >> > > > >
> > > > >> > > > > Given that I would also like to volunteer as 1.2 release
> > > > manager,
> > > > >> > > please
> > > > >> > > > > let me know your thoughts !
> > > > >> > > > >
> > > > >> > > > > Best,
> > > > >> > > > > Prashant Singh
> > > > >> > > > >
> > > > >> > > >
> > > > >> > >
> > > > >>
> > > > >
> > > >
> > >
> >
>
Re: DISCUSS: 1.2 release
Posted by Prashant Singh <pr...@snowflake.com.INVALID>.
Hey Jonas,
Thank you for bringing this up, i think we are still waiting on some of the
fixes which are required for 1.2
if its gets in by the time these get resolved, happy to include this in
1.2, though if its gonna take some more time or requires some further
discussion,
imho then we can wait for it 1.3 which would just next end of october, WDYT
?
Best,
Prashant Singh
On Fri, Sep 26, 2025 at 1:28 PM Honah J. <ho...@apache.org> wrote:
> Hi Prashant,
>
> Thanks for driving this! Sorry for the lateness that I did not realize
> that Python CLI binary distribution [2419] is not currently tracked in
> milestone 1.2.0. The goal is to make it easier for users to use our CLI to
> interact with polaris (with simple pip install instead of cloning the whole
> project). There has been much progress from Yong and Yufei and I think we
> are close. WDYT about including this to 1.2.0 milestone?
>
> [2419]: https://github.com/apache/polaris/issues/2419
> <https://github.com/apache/polaris/issues/2419>
>
> Thanks!
> Jonas
>
> On Fri, Sep 26, 2025 at 2:28 PM Dmitri Bourlatchkov <di...@apache.org>
> wrote:
>
> > Hi Prashant,
> >
> > I've also marked [2696] for 1.2.0. The reason is that it's a follow-up PR
> > to something that got recently merged to `main` and we need to resolve it
> > to avoid possible inconvenience (as discussed in the PRs).
> >
> > [2696] https://github.com/apache/polaris/pull/2696
> >
> > Cheers,
> > Dmitri.
> >
> > On Fri, Sep 26, 2025 at 12:40 PM Prashant Singh
> > <pr...@snowflake.com.invalid> wrote:
> >
> > > Thank you everyone ! for you inputs
> > > I see all PRs from Alex marked for 1.2 is merged, and as per feedback i
> > > moved issues / features marked for 1.2 to either 1.3 or simply removed
> > > milestones for the features we haven't started
> > > developing on.
> > > My current understanding is that we are waiting for :
> > > [1] PR - https://github.com/apache/polaris/pull/2653
> > > [2] Issue - https://github.com/apache/polaris/issues/2671 so that
> > rolling
> > > upgrades are handled correctly (we have a thread for this already)
> > >
> > > If this understanding is correct, then post resolution of [1] and [2]
> we
> > > should be good to move forward with 1.2 rc cut.
> > > Please let me know if I am missing anything, if all are ok i will track
> > > these 2 to move forward with 1.2 rc cut to continue our monthly release
> > > train model.
> > >
> > > Best,
> > > Prashant Singh
> > >
> > > On Tue, Sep 16, 2025 at 1:58 PM Prashant Singh <
> > > prashant.singh@snowflake.com>
> > > wrote:
> > >
> > > > Thank you JB & Alex !
> > > >
> > > > Re: semi automatic effort, I propose also to move forward on the GH
> > > > Release Action
> > > > if the GH Release Action is ready and happy to give it a spin !
> > > >
> > > > Re: I have proactively assigned the 1.2.0 milestone to some of my PRs
> > > that
> > > > I think could be part of 1.2.0.
> > > > Thank you Alex for also starting the thread for this ! I hope these
> get
> > > in
> > > > soon :) !
> > > >
> > > > Re: What do we want to do with remote signing?
> > > > I am not sure of next steps here, how about we see if we can get in
> by
> > > the
> > > > rc cutoff to catch 1.2 train.
> > > >
> > > > Again thank you everyone for your feedbacks looking forward to 1.2
> > > release
> > > >
> > > > I also added an iceberg version bump to 1.10 in this track, as our
> > tests
> > > > were failing with dependabot update, it will be nice to include this
> as
> > > > well !
> > > > https://github.com/apache/polaris/pull/2586
> > > >
> > > > Best,
> > > > Prashant Singh
> > > >
> > > >
> > > > On Tue, Sep 16, 2025 at 9:53 AM Alexandre Dutra <ad...@apache.org>
> > > wrote:
> > > >
> > > >> Hi Prashant, hi all,
> > > >>
> > > >> Thanks for driving the 1.2 release effort!
> > > >>
> > > >> I have proactively assigned the 1.2.0 milestone to some of my PRs
> that
> > > >> I think could be part of 1.2.0.
> > > >>
> > > >> What do we want to do with remote signing? I think we could include
> > > >> the current PR in experimental / preview state, but I'm fine holding
> > > >> off until we finish the implementation if you think that's safer.
> > > >>
> > > >> Thanks,
> > > >> Alex
> > > >>
> > > >> On Tue, Sep 16, 2025 at 8:06 AM Jean-Baptiste Onofré <
> jb@nanthrax.net
> > >
> > > >> wrote:
> > > >> >
> > > >> > Hi
> > > >> >
> > > >> > Thanks for starting this ! It makes to me.
> > > >> >
> > > >> > And yes, it makes sense to start the prep/triage now.
> > > >> >
> > > >> > As part of semi auromatic effort, I propose also to move forward
> on
> > > the
> > > >> GH
> > > >> > Release Action.
> > > >> >
> > > >> > Regards
> > > >> > JB
> > > >> >
> > > >> > Le mar. 16 sept. 2025 à 02:16, Prashant Singh
> > > >> > <pr...@snowflake.com.invalid> a écrit :
> > > >> >
> > > >> > > Ack ! Thank you for the feedback Dmitri !
> > > >> > > Tracking 1.2 milestones
> > > >> > > <
> > > >> > >
> > > >>
> > >
> >
> https://github.com/apache/polaris/issues?q=is%3Aissue%20state%3Aopen%20milestone%3A1.2.0
> > > >> > > >
> > > >> > > for the release (will check the current status of the tickets /
> > prs
> > > >> already
> > > >> > > tagged with the 1.2 release and check with all) seems reasonable
> > to
> > > >> me !
> > > >> > >
> > > >> > > Best,
> > > >> > > Prashant Singh
> > > >> > >
> > > >> > > On Mon, Sep 15, 2025 at 2:42 PM Dmitri Bourlatchkov <
> > > dimas@apache.org
> > > >> >
> > > >> > > wrote:
> > > >> > >
> > > >> > > > Thanks for volunteering to drive the 1.2 release, Prashant!
> > > >> > > >
> > > >> > > > I believe we previously discussed using the "release train"
> > model,
> > > >> so
> > > >> > > > whatever is committed by the branch time, gets released :)
> > > >> > > >
> > > >> > > > I propose to use the 1.2.0 GH milestone for tracking PRs and
> > > Issues
> > > >> that
> > > >> > > > need special attention during the 1.2 release (e.g. blockers).
> > > >> > > >
> > > >> > > > I believe this process worked fairly well for the 1.1.0
> release
> > :)
> > > >> > > >
> > > >> > > > Cheers,
> > > >> > > > Dmitri.
> > > >> > > >
> > > >> > > > On Mon, Sep 15, 2025 at 4:48 PM Prashant Singh
> > > >> > > > <pr...@snowflake.com.invalid> wrote:
> > > >> > > >
> > > >> > > > > Hey All,
> > > >> > > > >
> > > >> > > > > Thank you everyone for working on the 1.1 release now since
> it
> > > is
> > > >> > > > *almost*
> > > >> > > > > done and we planned on a monthly release cadence, I was
> > > wondering
> > > >> if we
> > > >> > > > > should start thinking of a 1.2 release and start working
> > towards
> > > >> > > > > identifying what we want to target for 1.2.
> > > >> > > > >
> > > >> > > > > Given that I would also like to volunteer as 1.2 release
> > > manager,
> > > >> > > please
> > > >> > > > > let me know your thoughts !
> > > >> > > > >
> > > >> > > > > Best,
> > > >> > > > > Prashant Singh
> > > >> > > > >
> > > >> > > >
> > > >> > >
> > > >>
> > > >
> > >
> >
>
Re: DISCUSS: 1.2 release
Posted by "Honah J." <ho...@apache.org>.
Hi Prashant,
Thanks for driving this! Sorry for the lateness that I did not realize
that Python CLI binary distribution [2419] is not currently tracked in
milestone 1.2.0. The goal is to make it easier for users to use our CLI to
interact with polaris (with simple pip install instead of cloning the whole
project). There has been much progress from Yong and Yufei and I think we
are close. WDYT about including this to 1.2.0 milestone?
[2419]: https://github.com/apache/polaris/issues/2419
<https://github.com/apache/polaris/issues/2419>
Thanks!
Jonas
On Fri, Sep 26, 2025 at 2:28 PM Dmitri Bourlatchkov <di...@apache.org>
wrote:
> Hi Prashant,
>
> I've also marked [2696] for 1.2.0. The reason is that it's a follow-up PR
> to something that got recently merged to `main` and we need to resolve it
> to avoid possible inconvenience (as discussed in the PRs).
>
> [2696] https://github.com/apache/polaris/pull/2696
>
> Cheers,
> Dmitri.
>
> On Fri, Sep 26, 2025 at 12:40 PM Prashant Singh
> <pr...@snowflake.com.invalid> wrote:
>
> > Thank you everyone ! for you inputs
> > I see all PRs from Alex marked for 1.2 is merged, and as per feedback i
> > moved issues / features marked for 1.2 to either 1.3 or simply removed
> > milestones for the features we haven't started
> > developing on.
> > My current understanding is that we are waiting for :
> > [1] PR - https://github.com/apache/polaris/pull/2653
> > [2] Issue - https://github.com/apache/polaris/issues/2671 so that
> rolling
> > upgrades are handled correctly (we have a thread for this already)
> >
> > If this understanding is correct, then post resolution of [1] and [2] we
> > should be good to move forward with 1.2 rc cut.
> > Please let me know if I am missing anything, if all are ok i will track
> > these 2 to move forward with 1.2 rc cut to continue our monthly release
> > train model.
> >
> > Best,
> > Prashant Singh
> >
> > On Tue, Sep 16, 2025 at 1:58 PM Prashant Singh <
> > prashant.singh@snowflake.com>
> > wrote:
> >
> > > Thank you JB & Alex !
> > >
> > > Re: semi automatic effort, I propose also to move forward on the GH
> > > Release Action
> > > if the GH Release Action is ready and happy to give it a spin !
> > >
> > > Re: I have proactively assigned the 1.2.0 milestone to some of my PRs
> > that
> > > I think could be part of 1.2.0.
> > > Thank you Alex for also starting the thread for this ! I hope these get
> > in
> > > soon :) !
> > >
> > > Re: What do we want to do with remote signing?
> > > I am not sure of next steps here, how about we see if we can get in by
> > the
> > > rc cutoff to catch 1.2 train.
> > >
> > > Again thank you everyone for your feedbacks looking forward to 1.2
> > release
> > >
> > > I also added an iceberg version bump to 1.10 in this track, as our
> tests
> > > were failing with dependabot update, it will be nice to include this as
> > > well !
> > > https://github.com/apache/polaris/pull/2586
> > >
> > > Best,
> > > Prashant Singh
> > >
> > >
> > > On Tue, Sep 16, 2025 at 9:53 AM Alexandre Dutra <ad...@apache.org>
> > wrote:
> > >
> > >> Hi Prashant, hi all,
> > >>
> > >> Thanks for driving the 1.2 release effort!
> > >>
> > >> I have proactively assigned the 1.2.0 milestone to some of my PRs that
> > >> I think could be part of 1.2.0.
> > >>
> > >> What do we want to do with remote signing? I think we could include
> > >> the current PR in experimental / preview state, but I'm fine holding
> > >> off until we finish the implementation if you think that's safer.
> > >>
> > >> Thanks,
> > >> Alex
> > >>
> > >> On Tue, Sep 16, 2025 at 8:06 AM Jean-Baptiste Onofré <jb@nanthrax.net
> >
> > >> wrote:
> > >> >
> > >> > Hi
> > >> >
> > >> > Thanks for starting this ! It makes to me.
> > >> >
> > >> > And yes, it makes sense to start the prep/triage now.
> > >> >
> > >> > As part of semi auromatic effort, I propose also to move forward on
> > the
> > >> GH
> > >> > Release Action.
> > >> >
> > >> > Regards
> > >> > JB
> > >> >
> > >> > Le mar. 16 sept. 2025 à 02:16, Prashant Singh
> > >> > <pr...@snowflake.com.invalid> a écrit :
> > >> >
> > >> > > Ack ! Thank you for the feedback Dmitri !
> > >> > > Tracking 1.2 milestones
> > >> > > <
> > >> > >
> > >>
> >
> https://github.com/apache/polaris/issues?q=is%3Aissue%20state%3Aopen%20milestone%3A1.2.0
> > >> > > >
> > >> > > for the release (will check the current status of the tickets /
> prs
> > >> already
> > >> > > tagged with the 1.2 release and check with all) seems reasonable
> to
> > >> me !
> > >> > >
> > >> > > Best,
> > >> > > Prashant Singh
> > >> > >
> > >> > > On Mon, Sep 15, 2025 at 2:42 PM Dmitri Bourlatchkov <
> > dimas@apache.org
> > >> >
> > >> > > wrote:
> > >> > >
> > >> > > > Thanks for volunteering to drive the 1.2 release, Prashant!
> > >> > > >
> > >> > > > I believe we previously discussed using the "release train"
> model,
> > >> so
> > >> > > > whatever is committed by the branch time, gets released :)
> > >> > > >
> > >> > > > I propose to use the 1.2.0 GH milestone for tracking PRs and
> > Issues
> > >> that
> > >> > > > need special attention during the 1.2 release (e.g. blockers).
> > >> > > >
> > >> > > > I believe this process worked fairly well for the 1.1.0 release
> :)
> > >> > > >
> > >> > > > Cheers,
> > >> > > > Dmitri.
> > >> > > >
> > >> > > > On Mon, Sep 15, 2025 at 4:48 PM Prashant Singh
> > >> > > > <pr...@snowflake.com.invalid> wrote:
> > >> > > >
> > >> > > > > Hey All,
> > >> > > > >
> > >> > > > > Thank you everyone for working on the 1.1 release now since it
> > is
> > >> > > > *almost*
> > >> > > > > done and we planned on a monthly release cadence, I was
> > wondering
> > >> if we
> > >> > > > > should start thinking of a 1.2 release and start working
> towards
> > >> > > > > identifying what we want to target for 1.2.
> > >> > > > >
> > >> > > > > Given that I would also like to volunteer as 1.2 release
> > manager,
> > >> > > please
> > >> > > > > let me know your thoughts !
> > >> > > > >
> > >> > > > > Best,
> > >> > > > > Prashant Singh
> > >> > > > >
> > >> > > >
> > >> > >
> > >>
> > >
> >
>
Re: DISCUSS: 1.2 release
Posted by Dmitri Bourlatchkov <di...@apache.org>.
Hi Prashant,
I've also marked [2696] for 1.2.0. The reason is that it's a follow-up PR
to something that got recently merged to `main` and we need to resolve it
to avoid possible inconvenience (as discussed in the PRs).
[2696] https://github.com/apache/polaris/pull/2696
Cheers,
Dmitri.
On Fri, Sep 26, 2025 at 12:40 PM Prashant Singh
<pr...@snowflake.com.invalid> wrote:
> Thank you everyone ! for you inputs
> I see all PRs from Alex marked for 1.2 is merged, and as per feedback i
> moved issues / features marked for 1.2 to either 1.3 or simply removed
> milestones for the features we haven't started
> developing on.
> My current understanding is that we are waiting for :
> [1] PR - https://github.com/apache/polaris/pull/2653
> [2] Issue - https://github.com/apache/polaris/issues/2671 so that rolling
> upgrades are handled correctly (we have a thread for this already)
>
> If this understanding is correct, then post resolution of [1] and [2] we
> should be good to move forward with 1.2 rc cut.
> Please let me know if I am missing anything, if all are ok i will track
> these 2 to move forward with 1.2 rc cut to continue our monthly release
> train model.
>
> Best,
> Prashant Singh
>
> On Tue, Sep 16, 2025 at 1:58 PM Prashant Singh <
> prashant.singh@snowflake.com>
> wrote:
>
> > Thank you JB & Alex !
> >
> > Re: semi automatic effort, I propose also to move forward on the GH
> > Release Action
> > if the GH Release Action is ready and happy to give it a spin !
> >
> > Re: I have proactively assigned the 1.2.0 milestone to some of my PRs
> that
> > I think could be part of 1.2.0.
> > Thank you Alex for also starting the thread for this ! I hope these get
> in
> > soon :) !
> >
> > Re: What do we want to do with remote signing?
> > I am not sure of next steps here, how about we see if we can get in by
> the
> > rc cutoff to catch 1.2 train.
> >
> > Again thank you everyone for your feedbacks looking forward to 1.2
> release
> >
> > I also added an iceberg version bump to 1.10 in this track, as our tests
> > were failing with dependabot update, it will be nice to include this as
> > well !
> > https://github.com/apache/polaris/pull/2586
> >
> > Best,
> > Prashant Singh
> >
> >
> > On Tue, Sep 16, 2025 at 9:53 AM Alexandre Dutra <ad...@apache.org>
> wrote:
> >
> >> Hi Prashant, hi all,
> >>
> >> Thanks for driving the 1.2 release effort!
> >>
> >> I have proactively assigned the 1.2.0 milestone to some of my PRs that
> >> I think could be part of 1.2.0.
> >>
> >> What do we want to do with remote signing? I think we could include
> >> the current PR in experimental / preview state, but I'm fine holding
> >> off until we finish the implementation if you think that's safer.
> >>
> >> Thanks,
> >> Alex
> >>
> >> On Tue, Sep 16, 2025 at 8:06 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> >> wrote:
> >> >
> >> > Hi
> >> >
> >> > Thanks for starting this ! It makes to me.
> >> >
> >> > And yes, it makes sense to start the prep/triage now.
> >> >
> >> > As part of semi auromatic effort, I propose also to move forward on
> the
> >> GH
> >> > Release Action.
> >> >
> >> > Regards
> >> > JB
> >> >
> >> > Le mar. 16 sept. 2025 à 02:16, Prashant Singh
> >> > <pr...@snowflake.com.invalid> a écrit :
> >> >
> >> > > Ack ! Thank you for the feedback Dmitri !
> >> > > Tracking 1.2 milestones
> >> > > <
> >> > >
> >>
> https://github.com/apache/polaris/issues?q=is%3Aissue%20state%3Aopen%20milestone%3A1.2.0
> >> > > >
> >> > > for the release (will check the current status of the tickets / prs
> >> already
> >> > > tagged with the 1.2 release and check with all) seems reasonable to
> >> me !
> >> > >
> >> > > Best,
> >> > > Prashant Singh
> >> > >
> >> > > On Mon, Sep 15, 2025 at 2:42 PM Dmitri Bourlatchkov <
> dimas@apache.org
> >> >
> >> > > wrote:
> >> > >
> >> > > > Thanks for volunteering to drive the 1.2 release, Prashant!
> >> > > >
> >> > > > I believe we previously discussed using the "release train" model,
> >> so
> >> > > > whatever is committed by the branch time, gets released :)
> >> > > >
> >> > > > I propose to use the 1.2.0 GH milestone for tracking PRs and
> Issues
> >> that
> >> > > > need special attention during the 1.2 release (e.g. blockers).
> >> > > >
> >> > > > I believe this process worked fairly well for the 1.1.0 release :)
> >> > > >
> >> > > > Cheers,
> >> > > > Dmitri.
> >> > > >
> >> > > > On Mon, Sep 15, 2025 at 4:48 PM Prashant Singh
> >> > > > <pr...@snowflake.com.invalid> wrote:
> >> > > >
> >> > > > > Hey All,
> >> > > > >
> >> > > > > Thank you everyone for working on the 1.1 release now since it
> is
> >> > > > *almost*
> >> > > > > done and we planned on a monthly release cadence, I was
> wondering
> >> if we
> >> > > > > should start thinking of a 1.2 release and start working towards
> >> > > > > identifying what we want to target for 1.2.
> >> > > > >
> >> > > > > Given that I would also like to volunteer as 1.2 release
> manager,
> >> > > please
> >> > > > > let me know your thoughts !
> >> > > > >
> >> > > > > Best,
> >> > > > > Prashant Singh
> >> > > > >
> >> > > >
> >> > >
> >>
> >
>
Re: DISCUSS: 1.2 release
Posted by Dmitri Bourlatchkov <di...@apache.org>.
HI Prashant,
I'm waiting for approvals on [2672] which was tagged for 1.2.9 via [2207]
some time ago.
I see that you moved [2207] out to 1.3.0. That is fair, however, given
that [2672] has been in review for 2 days and Dennis' comments were minor
(in my opinion). I'd appreciate it if it could be merged for 1.2.0. I
proactively added it to the 1.2.0 milestone for visibility.
We can keep doc changes for [2207] to later. I think it should be ok as
long as the basic code for non-STS S3 is in 1.2.0
WDYT?
[2207] https://github.com/apache/polaris/issues/2207
[2672] https://github.com/apache/polaris/pull/2672
Thanks,
Dmitri.
On Fri, Sep 26, 2025 at 12:40 PM Prashant Singh
<pr...@snowflake.com.invalid> wrote:
> Thank you everyone ! for you inputs
> I see all PRs from Alex marked for 1.2 is merged, and as per feedback i
> moved issues / features marked for 1.2 to either 1.3 or simply removed
> milestones for the features we haven't started
> developing on.
> My current understanding is that we are waiting for :
> [1] PR - https://github.com/apache/polaris/pull/2653
> [2] Issue - https://github.com/apache/polaris/issues/2671 so that rolling
> upgrades are handled correctly (we have a thread for this already)
>
> If this understanding is correct, then post resolution of [1] and [2] we
> should be good to move forward with 1.2 rc cut.
> Please let me know if I am missing anything, if all are ok i will track
> these 2 to move forward with 1.2 rc cut to continue our monthly release
> train model.
>
> Best,
> Prashant Singh
>
> On Tue, Sep 16, 2025 at 1:58 PM Prashant Singh <
> prashant.singh@snowflake.com>
> wrote:
>
> > Thank you JB & Alex !
> >
> > Re: semi automatic effort, I propose also to move forward on the GH
> > Release Action
> > if the GH Release Action is ready and happy to give it a spin !
> >
> > Re: I have proactively assigned the 1.2.0 milestone to some of my PRs
> that
> > I think could be part of 1.2.0.
> > Thank you Alex for also starting the thread for this ! I hope these get
> in
> > soon :) !
> >
> > Re: What do we want to do with remote signing?
> > I am not sure of next steps here, how about we see if we can get in by
> the
> > rc cutoff to catch 1.2 train.
> >
> > Again thank you everyone for your feedbacks looking forward to 1.2
> release
> >
> > I also added an iceberg version bump to 1.10 in this track, as our tests
> > were failing with dependabot update, it will be nice to include this as
> > well !
> > https://github.com/apache/polaris/pull/2586
> >
> > Best,
> > Prashant Singh
> >
> >
> > On Tue, Sep 16, 2025 at 9:53 AM Alexandre Dutra <ad...@apache.org>
> wrote:
> >
> >> Hi Prashant, hi all,
> >>
> >> Thanks for driving the 1.2 release effort!
> >>
> >> I have proactively assigned the 1.2.0 milestone to some of my PRs that
> >> I think could be part of 1.2.0.
> >>
> >> What do we want to do with remote signing? I think we could include
> >> the current PR in experimental / preview state, but I'm fine holding
> >> off until we finish the implementation if you think that's safer.
> >>
> >> Thanks,
> >> Alex
> >>
> >> On Tue, Sep 16, 2025 at 8:06 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> >> wrote:
> >> >
> >> > Hi
> >> >
> >> > Thanks for starting this ! It makes to me.
> >> >
> >> > And yes, it makes sense to start the prep/triage now.
> >> >
> >> > As part of semi auromatic effort, I propose also to move forward on
> the
> >> GH
> >> > Release Action.
> >> >
> >> > Regards
> >> > JB
> >> >
> >> > Le mar. 16 sept. 2025 à 02:16, Prashant Singh
> >> > <pr...@snowflake.com.invalid> a écrit :
> >> >
> >> > > Ack ! Thank you for the feedback Dmitri !
> >> > > Tracking 1.2 milestones
> >> > > <
> >> > >
> >>
> https://github.com/apache/polaris/issues?q=is%3Aissue%20state%3Aopen%20milestone%3A1.2.0
> >> > > >
> >> > > for the release (will check the current status of the tickets / prs
> >> already
> >> > > tagged with the 1.2 release and check with all) seems reasonable to
> >> me !
> >> > >
> >> > > Best,
> >> > > Prashant Singh
> >> > >
> >> > > On Mon, Sep 15, 2025 at 2:42 PM Dmitri Bourlatchkov <
> dimas@apache.org
> >> >
> >> > > wrote:
> >> > >
> >> > > > Thanks for volunteering to drive the 1.2 release, Prashant!
> >> > > >
> >> > > > I believe we previously discussed using the "release train" model,
> >> so
> >> > > > whatever is committed by the branch time, gets released :)
> >> > > >
> >> > > > I propose to use the 1.2.0 GH milestone for tracking PRs and
> Issues
> >> that
> >> > > > need special attention during the 1.2 release (e.g. blockers).
> >> > > >
> >> > > > I believe this process worked fairly well for the 1.1.0 release :)
> >> > > >
> >> > > > Cheers,
> >> > > > Dmitri.
> >> > > >
> >> > > > On Mon, Sep 15, 2025 at 4:48 PM Prashant Singh
> >> > > > <pr...@snowflake.com.invalid> wrote:
> >> > > >
> >> > > > > Hey All,
> >> > > > >
> >> > > > > Thank you everyone for working on the 1.1 release now since it
> is
> >> > > > *almost*
> >> > > > > done and we planned on a monthly release cadence, I was
> wondering
> >> if we
> >> > > > > should start thinking of a 1.2 release and start working towards
> >> > > > > identifying what we want to target for 1.2.
> >> > > > >
> >> > > > > Given that I would also like to volunteer as 1.2 release
> manager,
> >> > > please
> >> > > > > let me know your thoughts !
> >> > > > >
> >> > > > > Best,
> >> > > > > Prashant Singh
> >> > > > >
> >> > > >
> >> > >
> >>
> >
>
Re: DISCUSS: 1.2 release
Posted by Dmitri Bourlatchkov <di...@apache.org>.
I'm also merging https://github.com/apache/polaris/pull/2650 (Aurora DB)
pretty soon :)
Thanks to all who participated and especially to Fabio for the research and
implementation!
Cheers,
Dmitri.
On Fri, Sep 26, 2025 at 12:40 PM Prashant Singh
<pr...@snowflake.com.invalid> wrote:
> Thank you everyone ! for you inputs
> I see all PRs from Alex marked for 1.2 is merged, and as per feedback i
> moved issues / features marked for 1.2 to either 1.3 or simply removed
> milestones for the features we haven't started
> developing on.
> My current understanding is that we are waiting for :
> [1] PR - https://github.com/apache/polaris/pull/2653
> [2] Issue - https://github.com/apache/polaris/issues/2671 so that rolling
> upgrades are handled correctly (we have a thread for this already)
>
> If this understanding is correct, then post resolution of [1] and [2] we
> should be good to move forward with 1.2 rc cut.
> Please let me know if I am missing anything, if all are ok i will track
> these 2 to move forward with 1.2 rc cut to continue our monthly release
> train model.
>
> Best,
> Prashant Singh
>
> On Tue, Sep 16, 2025 at 1:58 PM Prashant Singh <
> prashant.singh@snowflake.com>
> wrote:
>
> > Thank you JB & Alex !
> >
> > Re: semi automatic effort, I propose also to move forward on the GH
> > Release Action
> > if the GH Release Action is ready and happy to give it a spin !
> >
> > Re: I have proactively assigned the 1.2.0 milestone to some of my PRs
> that
> > I think could be part of 1.2.0.
> > Thank you Alex for also starting the thread for this ! I hope these get
> in
> > soon :) !
> >
> > Re: What do we want to do with remote signing?
> > I am not sure of next steps here, how about we see if we can get in by
> the
> > rc cutoff to catch 1.2 train.
> >
> > Again thank you everyone for your feedbacks looking forward to 1.2
> release
> >
> > I also added an iceberg version bump to 1.10 in this track, as our tests
> > were failing with dependabot update, it will be nice to include this as
> > well !
> > https://github.com/apache/polaris/pull/2586
> >
> > Best,
> > Prashant Singh
> >
> >
> > On Tue, Sep 16, 2025 at 9:53 AM Alexandre Dutra <ad...@apache.org>
> wrote:
> >
> >> Hi Prashant, hi all,
> >>
> >> Thanks for driving the 1.2 release effort!
> >>
> >> I have proactively assigned the 1.2.0 milestone to some of my PRs that
> >> I think could be part of 1.2.0.
> >>
> >> What do we want to do with remote signing? I think we could include
> >> the current PR in experimental / preview state, but I'm fine holding
> >> off until we finish the implementation if you think that's safer.
> >>
> >> Thanks,
> >> Alex
> >>
> >> On Tue, Sep 16, 2025 at 8:06 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> >> wrote:
> >> >
> >> > Hi
> >> >
> >> > Thanks for starting this ! It makes to me.
> >> >
> >> > And yes, it makes sense to start the prep/triage now.
> >> >
> >> > As part of semi auromatic effort, I propose also to move forward on
> the
> >> GH
> >> > Release Action.
> >> >
> >> > Regards
> >> > JB
> >> >
> >> > Le mar. 16 sept. 2025 à 02:16, Prashant Singh
> >> > <pr...@snowflake.com.invalid> a écrit :
> >> >
> >> > > Ack ! Thank you for the feedback Dmitri !
> >> > > Tracking 1.2 milestones
> >> > > <
> >> > >
> >>
> https://github.com/apache/polaris/issues?q=is%3Aissue%20state%3Aopen%20milestone%3A1.2.0
> >> > > >
> >> > > for the release (will check the current status of the tickets / prs
> >> already
> >> > > tagged with the 1.2 release and check with all) seems reasonable to
> >> me !
> >> > >
> >> > > Best,
> >> > > Prashant Singh
> >> > >
> >> > > On Mon, Sep 15, 2025 at 2:42 PM Dmitri Bourlatchkov <
> dimas@apache.org
> >> >
> >> > > wrote:
> >> > >
> >> > > > Thanks for volunteering to drive the 1.2 release, Prashant!
> >> > > >
> >> > > > I believe we previously discussed using the "release train" model,
> >> so
> >> > > > whatever is committed by the branch time, gets released :)
> >> > > >
> >> > > > I propose to use the 1.2.0 GH milestone for tracking PRs and
> Issues
> >> that
> >> > > > need special attention during the 1.2 release (e.g. blockers).
> >> > > >
> >> > > > I believe this process worked fairly well for the 1.1.0 release :)
> >> > > >
> >> > > > Cheers,
> >> > > > Dmitri.
> >> > > >
> >> > > > On Mon, Sep 15, 2025 at 4:48 PM Prashant Singh
> >> > > > <pr...@snowflake.com.invalid> wrote:
> >> > > >
> >> > > > > Hey All,
> >> > > > >
> >> > > > > Thank you everyone for working on the 1.1 release now since it
> is
> >> > > > *almost*
> >> > > > > done and we planned on a monthly release cadence, I was
> wondering
> >> if we
> >> > > > > should start thinking of a 1.2 release and start working towards
> >> > > > > identifying what we want to target for 1.2.
> >> > > > >
> >> > > > > Given that I would also like to volunteer as 1.2 release
> manager,
> >> > > please
> >> > > > > let me know your thoughts !
> >> > > > >
> >> > > > > Best,
> >> > > > > Prashant Singh
> >> > > > >
> >> > > >
> >> > >
> >>
> >
>
Re: DISCUSS: 1.2 release
Posted by Prashant Singh <pr...@snowflake.com.INVALID>.
Thank you Dmitri,
I think prioritizing 1.2 release over 1.1.1 seems reasonable to me (give
that we are so close). Thank you for heads up on the additional PRs.
IMHO it's fair to keep the door for 1.1.1 open just in case we stumble upon
additional issues.
I am also thinking of floating when I have rc ready for 1.2 in the slack
channels in case we can find some volunteers who can help us test with
their dev / staging environment this release.
Will try doing additional due diligence from my end to see if we can ensure
1.2 as a stable release, without surprises
Best,
Prashant Singh
On Fri, Sep 26, 2025 at 11:14 AM Dmitri Bourlatchkov
<dm...@dremio.com.invalid> wrote:
> Hi Prashant,
>
> Cross-linking for visibility :
> https://lists.apache.org/thread/5d9rl1l2jflbbnrl12ofmczjbcw8qv89
>
> WDYT about including what is necessary to fix JDBC upgrades in 1.2.0 (and
> avoiding 1.1.1)?
>
> Note: I originally proposed 1.1.1 because I thought 1.2.0 was not due for a
> few more weeks :)
>
> Thanks,
> Dmitri.
>
> On Fri, Sep 26, 2025 at 12:40 PM Prashant Singh
> <pr...@snowflake.com.invalid> wrote:
>
> > Thank you everyone ! for you inputs
> > I see all PRs from Alex marked for 1.2 is merged, and as per feedback i
> > moved issues / features marked for 1.2 to either 1.3 or simply removed
> > milestones for the features we haven't started
> > developing on.
> > My current understanding is that we are waiting for :
> > [1] PR - https://github.com/apache/polaris/pull/2653
> > [2] Issue - https://github.com/apache/polaris/issues/2671 so that
> rolling
> > upgrades are handled correctly (we have a thread for this already)
> >
> > If this understanding is correct, then post resolution of [1] and [2] we
> > should be good to move forward with 1.2 rc cut.
> > Please let me know if I am missing anything, if all are ok i will track
> > these 2 to move forward with 1.2 rc cut to continue our monthly release
> > train model.
> >
> > Best,
> > Prashant Singh
> >
> > On Tue, Sep 16, 2025 at 1:58 PM Prashant Singh <
> > prashant.singh@snowflake.com>
> > wrote:
> >
> > > Thank you JB & Alex !
> > >
> > > Re: semi automatic effort, I propose also to move forward on the GH
> > > Release Action
> > > if the GH Release Action is ready and happy to give it a spin !
> > >
> > > Re: I have proactively assigned the 1.2.0 milestone to some of my PRs
> > that
> > > I think could be part of 1.2.0.
> > > Thank you Alex for also starting the thread for this ! I hope these get
> > in
> > > soon :) !
> > >
> > > Re: What do we want to do with remote signing?
> > > I am not sure of next steps here, how about we see if we can get in by
> > the
> > > rc cutoff to catch 1.2 train.
> > >
> > > Again thank you everyone for your feedbacks looking forward to 1.2
> > release
> > >
> > > I also added an iceberg version bump to 1.10 in this track, as our
> tests
> > > were failing with dependabot update, it will be nice to include this as
> > > well !
> > > https://github.com/apache/polaris/pull/2586
> > >
> > > Best,
> > > Prashant Singh
> > >
> > >
> > > On Tue, Sep 16, 2025 at 9:53 AM Alexandre Dutra <ad...@apache.org>
> > wrote:
> > >
> > >> Hi Prashant, hi all,
> > >>
> > >> Thanks for driving the 1.2 release effort!
> > >>
> > >> I have proactively assigned the 1.2.0 milestone to some of my PRs that
> > >> I think could be part of 1.2.0.
> > >>
> > >> What do we want to do with remote signing? I think we could include
> > >> the current PR in experimental / preview state, but I'm fine holding
> > >> off until we finish the implementation if you think that's safer.
> > >>
> > >> Thanks,
> > >> Alex
> > >>
> > >> On Tue, Sep 16, 2025 at 8:06 AM Jean-Baptiste Onofré <jb@nanthrax.net
> >
> > >> wrote:
> > >> >
> > >> > Hi
> > >> >
> > >> > Thanks for starting this ! It makes to me.
> > >> >
> > >> > And yes, it makes sense to start the prep/triage now.
> > >> >
> > >> > As part of semi auromatic effort, I propose also to move forward on
> > the
> > >> GH
> > >> > Release Action.
> > >> >
> > >> > Regards
> > >> > JB
> > >> >
> > >> > Le mar. 16 sept. 2025 à 02:16, Prashant Singh
> > >> > <pr...@snowflake.com.invalid> a écrit :
> > >> >
> > >> > > Ack ! Thank you for the feedback Dmitri !
> > >> > > Tracking 1.2 milestones
> > >> > > <
> > >> > >
> > >>
> >
> https://github.com/apache/polaris/issues?q=is%3Aissue%20state%3Aopen%20milestone%3A1.2.0
> > >> > > >
> > >> > > for the release (will check the current status of the tickets /
> prs
> > >> already
> > >> > > tagged with the 1.2 release and check with all) seems reasonable
> to
> > >> me !
> > >> > >
> > >> > > Best,
> > >> > > Prashant Singh
> > >> > >
> > >> > > On Mon, Sep 15, 2025 at 2:42 PM Dmitri Bourlatchkov <
> > dimas@apache.org
> > >> >
> > >> > > wrote:
> > >> > >
> > >> > > > Thanks for volunteering to drive the 1.2 release, Prashant!
> > >> > > >
> > >> > > > I believe we previously discussed using the "release train"
> model,
> > >> so
> > >> > > > whatever is committed by the branch time, gets released :)
> > >> > > >
> > >> > > > I propose to use the 1.2.0 GH milestone for tracking PRs and
> > Issues
> > >> that
> > >> > > > need special attention during the 1.2 release (e.g. blockers).
> > >> > > >
> > >> > > > I believe this process worked fairly well for the 1.1.0 release
> :)
> > >> > > >
> > >> > > > Cheers,
> > >> > > > Dmitri.
> > >> > > >
> > >> > > > On Mon, Sep 15, 2025 at 4:48 PM Prashant Singh
> > >> > > > <pr...@snowflake.com.invalid> wrote:
> > >> > > >
> > >> > > > > Hey All,
> > >> > > > >
> > >> > > > > Thank you everyone for working on the 1.1 release now since it
> > is
> > >> > > > *almost*
> > >> > > > > done and we planned on a monthly release cadence, I was
> > wondering
> > >> if we
> > >> > > > > should start thinking of a 1.2 release and start working
> towards
> > >> > > > > identifying what we want to target for 1.2.
> > >> > > > >
> > >> > > > > Given that I would also like to volunteer as 1.2 release
> > manager,
> > >> > > please
> > >> > > > > let me know your thoughts !
> > >> > > > >
> > >> > > > > Best,
> > >> > > > > Prashant Singh
> > >> > > > >
> > >> > > >
> > >> > >
> > >>
> > >
> >
>
Re: DISCUSS: 1.2 release
Posted by Dmitri Bourlatchkov <dm...@dremio.com.INVALID>.
Hi Prashant,
Cross-linking for visibility :
https://lists.apache.org/thread/5d9rl1l2jflbbnrl12ofmczjbcw8qv89
WDYT about including what is necessary to fix JDBC upgrades in 1.2.0 (and
avoiding 1.1.1)?
Note: I originally proposed 1.1.1 because I thought 1.2.0 was not due for a
few more weeks :)
Thanks,
Dmitri.
On Fri, Sep 26, 2025 at 12:40 PM Prashant Singh
<pr...@snowflake.com.invalid> wrote:
> Thank you everyone ! for you inputs
> I see all PRs from Alex marked for 1.2 is merged, and as per feedback i
> moved issues / features marked for 1.2 to either 1.3 or simply removed
> milestones for the features we haven't started
> developing on.
> My current understanding is that we are waiting for :
> [1] PR - https://github.com/apache/polaris/pull/2653
> [2] Issue - https://github.com/apache/polaris/issues/2671 so that rolling
> upgrades are handled correctly (we have a thread for this already)
>
> If this understanding is correct, then post resolution of [1] and [2] we
> should be good to move forward with 1.2 rc cut.
> Please let me know if I am missing anything, if all are ok i will track
> these 2 to move forward with 1.2 rc cut to continue our monthly release
> train model.
>
> Best,
> Prashant Singh
>
> On Tue, Sep 16, 2025 at 1:58 PM Prashant Singh <
> prashant.singh@snowflake.com>
> wrote:
>
> > Thank you JB & Alex !
> >
> > Re: semi automatic effort, I propose also to move forward on the GH
> > Release Action
> > if the GH Release Action is ready and happy to give it a spin !
> >
> > Re: I have proactively assigned the 1.2.0 milestone to some of my PRs
> that
> > I think could be part of 1.2.0.
> > Thank you Alex for also starting the thread for this ! I hope these get
> in
> > soon :) !
> >
> > Re: What do we want to do with remote signing?
> > I am not sure of next steps here, how about we see if we can get in by
> the
> > rc cutoff to catch 1.2 train.
> >
> > Again thank you everyone for your feedbacks looking forward to 1.2
> release
> >
> > I also added an iceberg version bump to 1.10 in this track, as our tests
> > were failing with dependabot update, it will be nice to include this as
> > well !
> > https://github.com/apache/polaris/pull/2586
> >
> > Best,
> > Prashant Singh
> >
> >
> > On Tue, Sep 16, 2025 at 9:53 AM Alexandre Dutra <ad...@apache.org>
> wrote:
> >
> >> Hi Prashant, hi all,
> >>
> >> Thanks for driving the 1.2 release effort!
> >>
> >> I have proactively assigned the 1.2.0 milestone to some of my PRs that
> >> I think could be part of 1.2.0.
> >>
> >> What do we want to do with remote signing? I think we could include
> >> the current PR in experimental / preview state, but I'm fine holding
> >> off until we finish the implementation if you think that's safer.
> >>
> >> Thanks,
> >> Alex
> >>
> >> On Tue, Sep 16, 2025 at 8:06 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> >> wrote:
> >> >
> >> > Hi
> >> >
> >> > Thanks for starting this ! It makes to me.
> >> >
> >> > And yes, it makes sense to start the prep/triage now.
> >> >
> >> > As part of semi auromatic effort, I propose also to move forward on
> the
> >> GH
> >> > Release Action.
> >> >
> >> > Regards
> >> > JB
> >> >
> >> > Le mar. 16 sept. 2025 à 02:16, Prashant Singh
> >> > <pr...@snowflake.com.invalid> a écrit :
> >> >
> >> > > Ack ! Thank you for the feedback Dmitri !
> >> > > Tracking 1.2 milestones
> >> > > <
> >> > >
> >>
> https://github.com/apache/polaris/issues?q=is%3Aissue%20state%3Aopen%20milestone%3A1.2.0
> >> > > >
> >> > > for the release (will check the current status of the tickets / prs
> >> already
> >> > > tagged with the 1.2 release and check with all) seems reasonable to
> >> me !
> >> > >
> >> > > Best,
> >> > > Prashant Singh
> >> > >
> >> > > On Mon, Sep 15, 2025 at 2:42 PM Dmitri Bourlatchkov <
> dimas@apache.org
> >> >
> >> > > wrote:
> >> > >
> >> > > > Thanks for volunteering to drive the 1.2 release, Prashant!
> >> > > >
> >> > > > I believe we previously discussed using the "release train" model,
> >> so
> >> > > > whatever is committed by the branch time, gets released :)
> >> > > >
> >> > > > I propose to use the 1.2.0 GH milestone for tracking PRs and
> Issues
> >> that
> >> > > > need special attention during the 1.2 release (e.g. blockers).
> >> > > >
> >> > > > I believe this process worked fairly well for the 1.1.0 release :)
> >> > > >
> >> > > > Cheers,
> >> > > > Dmitri.
> >> > > >
> >> > > > On Mon, Sep 15, 2025 at 4:48 PM Prashant Singh
> >> > > > <pr...@snowflake.com.invalid> wrote:
> >> > > >
> >> > > > > Hey All,
> >> > > > >
> >> > > > > Thank you everyone for working on the 1.1 release now since it
> is
> >> > > > *almost*
> >> > > > > done and we planned on a monthly release cadence, I was
> wondering
> >> if we
> >> > > > > should start thinking of a 1.2 release and start working towards
> >> > > > > identifying what we want to target for 1.2.
> >> > > > >
> >> > > > > Given that I would also like to volunteer as 1.2 release
> manager,
> >> > > please
> >> > > > > let me know your thoughts !
> >> > > > >
> >> > > > > Best,
> >> > > > > Prashant Singh
> >> > > > >
> >> > > >
> >> > >
> >>
> >
>
Re: DISCUSS: 1.2 release
Posted by Prashant Singh <pr...@snowflake.com.INVALID>.
Thank you everyone ! for you inputs
I see all PRs from Alex marked for 1.2 is merged, and as per feedback i
moved issues / features marked for 1.2 to either 1.3 or simply removed
milestones for the features we haven't started
developing on.
My current understanding is that we are waiting for :
[1] PR - https://github.com/apache/polaris/pull/2653
[2] Issue - https://github.com/apache/polaris/issues/2671 so that rolling
upgrades are handled correctly (we have a thread for this already)
If this understanding is correct, then post resolution of [1] and [2] we
should be good to move forward with 1.2 rc cut.
Please let me know if I am missing anything, if all are ok i will track
these 2 to move forward with 1.2 rc cut to continue our monthly release
train model.
Best,
Prashant Singh
On Tue, Sep 16, 2025 at 1:58 PM Prashant Singh <pr...@snowflake.com>
wrote:
> Thank you JB & Alex !
>
> Re: semi automatic effort, I propose also to move forward on the GH
> Release Action
> if the GH Release Action is ready and happy to give it a spin !
>
> Re: I have proactively assigned the 1.2.0 milestone to some of my PRs that
> I think could be part of 1.2.0.
> Thank you Alex for also starting the thread for this ! I hope these get in
> soon :) !
>
> Re: What do we want to do with remote signing?
> I am not sure of next steps here, how about we see if we can get in by the
> rc cutoff to catch 1.2 train.
>
> Again thank you everyone for your feedbacks looking forward to 1.2 release
>
> I also added an iceberg version bump to 1.10 in this track, as our tests
> were failing with dependabot update, it will be nice to include this as
> well !
> https://github.com/apache/polaris/pull/2586
>
> Best,
> Prashant Singh
>
>
> On Tue, Sep 16, 2025 at 9:53 AM Alexandre Dutra <ad...@apache.org> wrote:
>
>> Hi Prashant, hi all,
>>
>> Thanks for driving the 1.2 release effort!
>>
>> I have proactively assigned the 1.2.0 milestone to some of my PRs that
>> I think could be part of 1.2.0.
>>
>> What do we want to do with remote signing? I think we could include
>> the current PR in experimental / preview state, but I'm fine holding
>> off until we finish the implementation if you think that's safer.
>>
>> Thanks,
>> Alex
>>
>> On Tue, Sep 16, 2025 at 8:06 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
>> wrote:
>> >
>> > Hi
>> >
>> > Thanks for starting this ! It makes to me.
>> >
>> > And yes, it makes sense to start the prep/triage now.
>> >
>> > As part of semi auromatic effort, I propose also to move forward on the
>> GH
>> > Release Action.
>> >
>> > Regards
>> > JB
>> >
>> > Le mar. 16 sept. 2025 à 02:16, Prashant Singh
>> > <pr...@snowflake.com.invalid> a écrit :
>> >
>> > > Ack ! Thank you for the feedback Dmitri !
>> > > Tracking 1.2 milestones
>> > > <
>> > >
>> https://github.com/apache/polaris/issues?q=is%3Aissue%20state%3Aopen%20milestone%3A1.2.0
>> > > >
>> > > for the release (will check the current status of the tickets / prs
>> already
>> > > tagged with the 1.2 release and check with all) seems reasonable to
>> me !
>> > >
>> > > Best,
>> > > Prashant Singh
>> > >
>> > > On Mon, Sep 15, 2025 at 2:42 PM Dmitri Bourlatchkov <dimas@apache.org
>> >
>> > > wrote:
>> > >
>> > > > Thanks for volunteering to drive the 1.2 release, Prashant!
>> > > >
>> > > > I believe we previously discussed using the "release train" model,
>> so
>> > > > whatever is committed by the branch time, gets released :)
>> > > >
>> > > > I propose to use the 1.2.0 GH milestone for tracking PRs and Issues
>> that
>> > > > need special attention during the 1.2 release (e.g. blockers).
>> > > >
>> > > > I believe this process worked fairly well for the 1.1.0 release :)
>> > > >
>> > > > Cheers,
>> > > > Dmitri.
>> > > >
>> > > > On Mon, Sep 15, 2025 at 4:48 PM Prashant Singh
>> > > > <pr...@snowflake.com.invalid> wrote:
>> > > >
>> > > > > Hey All,
>> > > > >
>> > > > > Thank you everyone for working on the 1.1 release now since it is
>> > > > *almost*
>> > > > > done and we planned on a monthly release cadence, I was wondering
>> if we
>> > > > > should start thinking of a 1.2 release and start working towards
>> > > > > identifying what we want to target for 1.2.
>> > > > >
>> > > > > Given that I would also like to volunteer as 1.2 release manager,
>> > > please
>> > > > > let me know your thoughts !
>> > > > >
>> > > > > Best,
>> > > > > Prashant Singh
>> > > > >
>> > > >
>> > >
>>
>
Re: DISCUSS: 1.2 release
Posted by Prashant Singh <pr...@snowflake.com.INVALID>.
Thank you JB & Alex !
Re: semi automatic effort, I propose also to move forward on the GH Release
Action
if the GH Release Action is ready and happy to give it a spin !
Re: I have proactively assigned the 1.2.0 milestone to some of my PRs that
I think could be part of 1.2.0.
Thank you Alex for also starting the thread for this ! I hope these get in
soon :) !
Re: What do we want to do with remote signing?
I am not sure of next steps here, how about we see if we can get in by the
rc cutoff to catch 1.2 train.
Again thank you everyone for your feedbacks looking forward to 1.2 release
I also added an iceberg version bump to 1.10 in this track, as our tests
were failing with dependabot update, it will be nice to include this as
well !
https://github.com/apache/polaris/pull/2586
Best,
Prashant Singh
On Tue, Sep 16, 2025 at 9:53 AM Alexandre Dutra <ad...@apache.org> wrote:
> Hi Prashant, hi all,
>
> Thanks for driving the 1.2 release effort!
>
> I have proactively assigned the 1.2.0 milestone to some of my PRs that
> I think could be part of 1.2.0.
>
> What do we want to do with remote signing? I think we could include
> the current PR in experimental / preview state, but I'm fine holding
> off until we finish the implementation if you think that's safer.
>
> Thanks,
> Alex
>
> On Tue, Sep 16, 2025 at 8:06 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
> >
> > Hi
> >
> > Thanks for starting this ! It makes to me.
> >
> > And yes, it makes sense to start the prep/triage now.
> >
> > As part of semi auromatic effort, I propose also to move forward on the
> GH
> > Release Action.
> >
> > Regards
> > JB
> >
> > Le mar. 16 sept. 2025 à 02:16, Prashant Singh
> > <pr...@snowflake.com.invalid> a écrit :
> >
> > > Ack ! Thank you for the feedback Dmitri !
> > > Tracking 1.2 milestones
> > > <
> > >
> https://github.com/apache/polaris/issues?q=is%3Aissue%20state%3Aopen%20milestone%3A1.2.0
> > > >
> > > for the release (will check the current status of the tickets / prs
> already
> > > tagged with the 1.2 release and check with all) seems reasonable to me
> !
> > >
> > > Best,
> > > Prashant Singh
> > >
> > > On Mon, Sep 15, 2025 at 2:42 PM Dmitri Bourlatchkov <di...@apache.org>
> > > wrote:
> > >
> > > > Thanks for volunteering to drive the 1.2 release, Prashant!
> > > >
> > > > I believe we previously discussed using the "release train" model, so
> > > > whatever is committed by the branch time, gets released :)
> > > >
> > > > I propose to use the 1.2.0 GH milestone for tracking PRs and Issues
> that
> > > > need special attention during the 1.2 release (e.g. blockers).
> > > >
> > > > I believe this process worked fairly well for the 1.1.0 release :)
> > > >
> > > > Cheers,
> > > > Dmitri.
> > > >
> > > > On Mon, Sep 15, 2025 at 4:48 PM Prashant Singh
> > > > <pr...@snowflake.com.invalid> wrote:
> > > >
> > > > > Hey All,
> > > > >
> > > > > Thank you everyone for working on the 1.1 release now since it is
> > > > *almost*
> > > > > done and we planned on a monthly release cadence, I was wondering
> if we
> > > > > should start thinking of a 1.2 release and start working towards
> > > > > identifying what we want to target for 1.2.
> > > > >
> > > > > Given that I would also like to volunteer as 1.2 release manager,
> > > please
> > > > > let me know your thoughts !
> > > > >
> > > > > Best,
> > > > > Prashant Singh
> > > > >
> > > >
> > >
>
Re: DISCUSS: 1.2 release
Posted by Alexandre Dutra <ad...@apache.org>.
Hi Prashant, hi all,
Thanks for driving the 1.2 release effort!
I have proactively assigned the 1.2.0 milestone to some of my PRs that
I think could be part of 1.2.0.
What do we want to do with remote signing? I think we could include
the current PR in experimental / preview state, but I'm fine holding
off until we finish the implementation if you think that's safer.
Thanks,
Alex
On Tue, Sep 16, 2025 at 8:06 AM Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>
> Hi
>
> Thanks for starting this ! It makes to me.
>
> And yes, it makes sense to start the prep/triage now.
>
> As part of semi auromatic effort, I propose also to move forward on the GH
> Release Action.
>
> Regards
> JB
>
> Le mar. 16 sept. 2025 à 02:16, Prashant Singh
> <pr...@snowflake.com.invalid> a écrit :
>
> > Ack ! Thank you for the feedback Dmitri !
> > Tracking 1.2 milestones
> > <
> > https://github.com/apache/polaris/issues?q=is%3Aissue%20state%3Aopen%20milestone%3A1.2.0
> > >
> > for the release (will check the current status of the tickets / prs already
> > tagged with the 1.2 release and check with all) seems reasonable to me !
> >
> > Best,
> > Prashant Singh
> >
> > On Mon, Sep 15, 2025 at 2:42 PM Dmitri Bourlatchkov <di...@apache.org>
> > wrote:
> >
> > > Thanks for volunteering to drive the 1.2 release, Prashant!
> > >
> > > I believe we previously discussed using the "release train" model, so
> > > whatever is committed by the branch time, gets released :)
> > >
> > > I propose to use the 1.2.0 GH milestone for tracking PRs and Issues that
> > > need special attention during the 1.2 release (e.g. blockers).
> > >
> > > I believe this process worked fairly well for the 1.1.0 release :)
> > >
> > > Cheers,
> > > Dmitri.
> > >
> > > On Mon, Sep 15, 2025 at 4:48 PM Prashant Singh
> > > <pr...@snowflake.com.invalid> wrote:
> > >
> > > > Hey All,
> > > >
> > > > Thank you everyone for working on the 1.1 release now since it is
> > > *almost*
> > > > done and we planned on a monthly release cadence, I was wondering if we
> > > > should start thinking of a 1.2 release and start working towards
> > > > identifying what we want to target for 1.2.
> > > >
> > > > Given that I would also like to volunteer as 1.2 release manager,
> > please
> > > > let me know your thoughts !
> > > >
> > > > Best,
> > > > Prashant Singh
> > > >
> > >
> >
Re: DISCUSS: 1.2 release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi
Thanks for starting this ! It makes to me.
And yes, it makes sense to start the prep/triage now.
As part of semi auromatic effort, I propose also to move forward on the GH
Release Action.
Regards
JB
Le mar. 16 sept. 2025 à 02:16, Prashant Singh
<pr...@snowflake.com.invalid> a écrit :
> Ack ! Thank you for the feedback Dmitri !
> Tracking 1.2 milestones
> <
> https://github.com/apache/polaris/issues?q=is%3Aissue%20state%3Aopen%20milestone%3A1.2.0
> >
> for the release (will check the current status of the tickets / prs already
> tagged with the 1.2 release and check with all) seems reasonable to me !
>
> Best,
> Prashant Singh
>
> On Mon, Sep 15, 2025 at 2:42 PM Dmitri Bourlatchkov <di...@apache.org>
> wrote:
>
> > Thanks for volunteering to drive the 1.2 release, Prashant!
> >
> > I believe we previously discussed using the "release train" model, so
> > whatever is committed by the branch time, gets released :)
> >
> > I propose to use the 1.2.0 GH milestone for tracking PRs and Issues that
> > need special attention during the 1.2 release (e.g. blockers).
> >
> > I believe this process worked fairly well for the 1.1.0 release :)
> >
> > Cheers,
> > Dmitri.
> >
> > On Mon, Sep 15, 2025 at 4:48 PM Prashant Singh
> > <pr...@snowflake.com.invalid> wrote:
> >
> > > Hey All,
> > >
> > > Thank you everyone for working on the 1.1 release now since it is
> > *almost*
> > > done and we planned on a monthly release cadence, I was wondering if we
> > > should start thinking of a 1.2 release and start working towards
> > > identifying what we want to target for 1.2.
> > >
> > > Given that I would also like to volunteer as 1.2 release manager,
> please
> > > let me know your thoughts !
> > >
> > > Best,
> > > Prashant Singh
> > >
> >
>
Re: DISCUSS: 1.2 release
Posted by Prashant Singh <pr...@snowflake.com.INVALID>.
Ack ! Thank you for the feedback Dmitri !
Tracking 1.2 milestones
<https://github.com/apache/polaris/issues?q=is%3Aissue%20state%3Aopen%20milestone%3A1.2.0>
for the release (will check the current status of the tickets / prs already
tagged with the 1.2 release and check with all) seems reasonable to me !
Best,
Prashant Singh
On Mon, Sep 15, 2025 at 2:42 PM Dmitri Bourlatchkov <di...@apache.org>
wrote:
> Thanks for volunteering to drive the 1.2 release, Prashant!
>
> I believe we previously discussed using the "release train" model, so
> whatever is committed by the branch time, gets released :)
>
> I propose to use the 1.2.0 GH milestone for tracking PRs and Issues that
> need special attention during the 1.2 release (e.g. blockers).
>
> I believe this process worked fairly well for the 1.1.0 release :)
>
> Cheers,
> Dmitri.
>
> On Mon, Sep 15, 2025 at 4:48 PM Prashant Singh
> <pr...@snowflake.com.invalid> wrote:
>
> > Hey All,
> >
> > Thank you everyone for working on the 1.1 release now since it is
> *almost*
> > done and we planned on a monthly release cadence, I was wondering if we
> > should start thinking of a 1.2 release and start working towards
> > identifying what we want to target for 1.2.
> >
> > Given that I would also like to volunteer as 1.2 release manager, please
> > let me know your thoughts !
> >
> > Best,
> > Prashant Singh
> >
>
Re: DISCUSS: 1.2 release
Posted by Dmitri Bourlatchkov <di...@apache.org>.
Thanks for volunteering to drive the 1.2 release, Prashant!
I believe we previously discussed using the "release train" model, so
whatever is committed by the branch time, gets released :)
I propose to use the 1.2.0 GH milestone for tracking PRs and Issues that
need special attention during the 1.2 release (e.g. blockers).
I believe this process worked fairly well for the 1.1.0 release :)
Cheers,
Dmitri.
On Mon, Sep 15, 2025 at 4:48 PM Prashant Singh
<pr...@snowflake.com.invalid> wrote:
> Hey All,
>
> Thank you everyone for working on the 1.1 release now since it is *almost*
> done and we planned on a monthly release cadence, I was wondering if we
> should start thinking of a 1.2 release and start working towards
> identifying what we want to target for 1.2.
>
> Given that I would also like to volunteer as 1.2 release manager, please
> let me know your thoughts !
>
> Best,
> Prashant Singh
>
Re: DISCUSS: 1.2 release
Posted by Yufei Gu <fl...@gmail.com>.
Thanks Prashant for volunteering. It's the right time to get started with
the 1.2 release. I'd suggest setting ETA to the end of October, given the
1.1 is not out yet, and it's September 15th already.
Yufei
On Mon, Sep 15, 2025 at 1:48 PM Prashant Singh
<pr...@snowflake.com.invalid> wrote:
> Hey All,
>
> Thank you everyone for working on the 1.1 release now since it is *almost*
> done and we planned on a monthly release cadence, I was wondering if we
> should start thinking of a 1.2 release and start working towards
> identifying what we want to target for 1.2.
>
> Given that I would also like to volunteer as 1.2 release manager, please
> let me know your thoughts !
>
> Best,
> Prashant Singh
>