The Infra team has resolved my ticket. https://issues.apache.org/jira/browse/INFRA-26985
So, it should be working as per our expectations now. I have pinged some contributors (who are not committers) to validate it. - Ajantha On Fri, Jul 4, 2025 at 4:33 PM Robert Stupp <sn...@snazy.de> wrote: > Argh, sorry, I misread the date - it's July 3rd, not the 25th of the > previous month :facepalm: > > On 7/4/25 12:48, Ajantha Bhat wrote: > >> This vote is running for ~10 days now, guess it's time to count the > > Sorry, I might have missed the other official discussion. I officially > > started this vote thread on July 3rd. > > > > That said, we do have enough binding votes. (+1: 4, -1: 0, 0:0). > > Therefore the vote has passed. > > > > - Ajantha > > > > On Fri, Jul 4, 2025 at 3:57 PM Robert Stupp <sn...@snazy.de> wrote: > > > >> +1 > >> > >> This vote is running for ~10 days now, guess it's time to count the > >> votes. I only see +1s, so go ahead? ;) > >> > >> On 7/3/25 07:29, Ajantha Bhat wrote: > >>> Hello, everyone. > >>> I'm starting this thread to discuss the possibility of changing the CI > >>> settings for apache/polaris to only require approval for new > >> contributors. > >>> This will improve the experience for our contributors. We do not have > >>> self-hosted runners, so there is no attack surface from the actions > side. > >>> > >>> Additionally, apache/polaris does not involve many heavy load CI tasks. > >>> Enabling it for PRs by default does not add to the overall burden on > ASF > >>> runners. > >>> I think this change could speed up our iteration process. > >>> > >>> Note: We already follow this style at apache iceberg and it worked > great > >> so > >>> far for contributors and the community. > >>> > >>> I will open an INFRA team ticket at ASF once we have enough binding > votes > >>> on this. > >>> > >>> - Ajantha > >>> > >> -- > >> Robert Stupp > >> @snazy > >> > >> > -- > Robert Stupp > @snazy > >
