Re: [VOTE] Use renovatebot weekly schedule

2025-03-03 Thread Jean-Baptiste Onofré
The vote failed: we have a veto from one PPMC member. So I close the vote and don’t do any change on renovatebot config. Regards JB Le lun. 3 mars 2025 à 19:04, Eric Maynard a écrit : > Is this vote closed? > > On Tue, Feb 25, 2025 at 10:53 AM Eric Maynard > wrote: > > > > Weekly updates will

Re: [VOTE] Use renovatebot weekly schedule

2025-03-03 Thread Eric Maynard
Is this vote closed? On Tue, Feb 25, 2025 at 10:53 AM Eric Maynard wrote: > > Weekly updates will _increase_ the amount of "noise" ... If all people > are fine with more noise, let's go for it > > That does seem to be what the votes reflect. > > On Tue, Feb 25, 2025 at 7:11 AM Dmitri Bourlatchko

Re: [VOTE] Use renovatebot weekly schedule

2025-02-25 Thread Eric Maynard
> Weekly updates will _increase_ the amount of "noise" ... If all people are fine with more noise, let's go for it That does seem to be what the votes reflect. On Tue, Feb 25, 2025 at 7:11 AM Dmitri Bourlatchkov wrote: > What was probably not considered at all: Weekly updates will _increase_ >

Re: [VOTE] Use renovatebot weekly schedule

2025-02-25 Thread Dmitri Bourlatchkov
What was probably not considered at all: Weekly updates will _increase_ the amount of "noise". Just think about it: Renovate creates all updates at once - once one change is merged, Renovate will rebase/recreate all other updates, CI will run again for all the other updates. Do we have to rebase

Re: [VOTE] Use renovatebot weekly schedule

2025-02-25 Thread Jean-Baptiste Onofré
The vote is only about weekly schedule (not grouping). I mentioned grouping to reduce the number of PRs but I’m more in favor of keeping atomic PRs. Regards JB Le mar. 25 févr. 2025 à 11:09, Robert Stupp a écrit : > > On 24.02.25 10:54, Jean-Baptiste Onofré wrote: > > Hi Robert, > > > > As your

Re: [VOTE] Use renovatebot weekly schedule

2025-02-25 Thread Robert Stupp
On 24.02.25 10:54, Jean-Baptiste Onofré wrote: Hi Robert, As your vote is binding, and this vote is a code modification change, it basically means veto. Let me try to convince you to revert your vote ;) You are maybe right about the noise, but worth a try. I think that grouping + weekly sched

Re: [VOTE] Use renovatebot weekly schedule

2025-02-24 Thread Jean-Baptiste Onofré
Hi Robert, As your vote is binding, and this vote is a code modification change, it basically means veto. Let me try to convince you to revert your vote ;) You are maybe right about the noise, but worth a try. I think that grouping + weekly schedule should reduce the noise. About keeping depende

Re: [VOTE] Use renovatebot weekly schedule

2025-02-24 Thread Jean-Baptiste Onofré
+1 (binding) Regards JB On Fri, Feb 21, 2025 at 2:38 PM Jean-Baptiste Onofré 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 renovatebo

Re: [VOTE] Use renovatebot weekly schedule

2025-02-23 Thread Robert Stupp
Keeping dependencies up-to-date is mandatory to get bug and security fixes as fast as possible and avoid piling up tech debt and CVEs from outdated dependencies. Moving to a weekly schedule would _not_ reduce that noise but instead _increase_ it and imply _more_ work to the few persons who dea

Re: [VOTE] Use renovatebot weekly schedule

2025-02-21 Thread Russell Spitzer
+1 On Fri, Feb 21, 2025 at 11:31 AM Eric Maynard wrote: > Obligatory +1 as it's my issue -- I'm also open to less frequent. > > My pitch: This is an upper bound on how often we update dependencies, not a > lower bound. If an actual person sees an actual reason to update a > dependency, they can

Re: [VOTE] Use renovatebot weekly schedule

2025-02-21 Thread Yufei Gu
+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é wrote: > By the way, the vote runs for 72 hours. > > Regards > JB > > On Fri, Feb 21, 2025 at 2:38 PM Jean-Baptiste Onofré > wrote: > > > > Hi folks, > > > > I know it

Re: [VOTE] Use renovatebot weekly schedule

2025-02-21 Thread Eric Maynard
Obligatory +1 as it's my issue -- I'm also open to less frequent. My pitch: This is an upper bound on how often we update dependencies, not a lower bound. If an actual person sees an actual reason to update a dependency, they can and should still do that :) --EM On Fri, Feb 21, 2025 at 9:27 AM A

Re: [VOTE] Use renovatebot weekly schedule

2025-02-21 Thread Alex Dutra
+0 as well, I am not bothered by Renovate at all personally. On Fri, Feb 21, 2025 at 6:16 PM Dmitri Bourlatchkov wrote: > +0 -- Renovate "noise" does not bother me personally, but I'm ok with less > frequent updates. > > Cheers, > Dmitri. > > On Fri, Feb 21, 2025 at 8:41 AM Jean-Baptiste Onofré

Re: [VOTE] Use renovatebot weekly schedule

2025-02-21 Thread Tyler Akidau
+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 wrote: > +0. I'd prefer an even less frequent one, like bi-we

Re: [VOTE] Use renovatebot weekly schedule

2025-02-21 Thread Dmitri Bourlatchkov
+0 -- Renovate "noise" does not bother me personally, but I'm ok with less frequent updates. Cheers, Dmitri. On Fri, Feb 21, 2025 at 8:41 AM Jean-Baptiste Onofré wrote: > Hi folks, > > I know it's a hot topic, but I would like to avoid any frustration in > our community. > > Before the vote, le

Re: [VOTE] Use renovatebot weekly schedule

2025-02-21 Thread Jean-Baptiste Onofré
By the way, the vote runs for 72 hours. Regards JB On Fri, Feb 21, 2025 at 2:38 PM Jean-Baptiste Onofré 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 updat

[VOTE] Use renovatebot weekly schedule

2025-02-21 Thread Jean-Baptiste Onofré
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