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 <[email protected]> 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 < > [email protected]> > 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 <[email protected]> > 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é <[email protected]> > >> 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 > >> > <[email protected]> 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 < > [email protected] > >> > > >> > > 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 > >> > > > <[email protected]> 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 > >> > > > > > >> > > > > >> > > > >> > > >
