+1 I don't see the value in the noise from the current config. I'm not opposed to bi-weekly as Yufei suggests either, but I see weekly as a strict improvement, so am +1 on this vote.
-Tyler On Fri, Feb 21, 2025 at 11:41 AM Yufei Gu <flyrain...@gmail.com> wrote: > +0. I'd prefer an even less frequent one, like bi-weekly schedule. > > Yufei > > > On Fri, Feb 21, 2025 at 5:54 AM Jean-Baptiste Onofré <j...@nanthrax.net> > wrote: > > > By the way, the vote runs for 72 hours. > > > > Regards > > JB > > > > On Fri, Feb 21, 2025 at 2:38 PM Jean-Baptiste Onofré <j...@nanthrax.net> > > wrote: > > > > > > Hi folks, > > > > > > I know it's a hot topic, but I would like to avoid any frustration in > > > our community. > > > > > > Before the vote, let me put some context. > > > > > > To manage our dependency updates, we are using renovatebot. > > > The current renovatebot configuration uses "at any time" schedule > > > (e.g. * * * * * cron), except for AWS SDK and boto3 updates which run > > > weekly. > > > Some contributors are complaining about the "noise" generated by > > renovatebot. > > > In order to "mitigate" that, we introduced "polaris-renovate" label to > > > easily filter the notification coming from renovatebot. > > > However, an issue has been created 4 days ago > > > (https://github.com/apache/polaris/issues/1018), meaning the "issue" > > > is still there. > > > > > > So, I propose this vote to have clear feedback from the community, as > > > we don't have clear lazy consensus. > > > > > > The vote is to schedule renovatebot update weekly: > > > > > > [ ] +1 - Use weekly schedule for all renovatebot updates > > > [ ] 0 > > > [ ] -1 - Don't use weekly schedule, keep the "at any time" schedule > > > > > > Thanks, > > > Regards > > > JB > > > > > > NB: we can consider this vote as a code modification vote (see > > > > https://www.apache.org/foundation/voting.html#votes-on-code-modification > > ). > > >
