Belated +1 from me as well. On the side discussion, I agree with JB that it is fine to include the community list. I don't think that causes trouble for anyone on the IPMC side, right? The IPMC doesn't see the podling vote and the podling knows that an IPMC vote is required. And it is still valid for the community -- in this case the podling members -- to vote on the IPMC thread. I don't see a downside or potential for confusion, and if anyone asks then it is a good opportunity for those of us on the incubator side to share context about how incubation works and why there are multiple votes.
Ryan On Thu, Oct 23, 2025 at 10:40 AM Prashant Singh <[email protected]> wrote: > Thank you everyone for voting, > we got 4 binding +1s (Kent, Francois, Romain, JB) with 0 -1s in 72 hours > This vote is passed. > I will send a RESULT email informing both the communities. > > On Tue, Oct 21, 2025 at 5:58 AM Jean-Baptiste Onofré <[email protected]> > wrote: > > > Hi Justin > > > > My bad, I always add the podling in cc to keep the "community" and > > release manager aware of the vote (especially if there's -1 vote, it's > > important to understand the vote). > > I thought it's convenient :) > > > > Regards > > JB > > > > On Tue, Oct 21, 2025 at 2:35 PM Justin Mclean <[email protected]> > > wrote: > > > > > > Hi JB, > > > > > > Only the IPMC list should be used for this. Votes in the Incubator > > follow a two-stage process: first, the podling community can hold a > > discussion and vote on their dev@ list, but the binding vote must occur > > on the [email protected] list. Adding the dev list here could > > create confusion about which vote is official and where binding votes are > > being cast. > > > > > > Kind Regards, > > > Justin > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
