Re: [MAINTAINERS SUMMIT] [3/4] Elevate handling of regressions that made it to releases deemed for end users

Thorsten Leemhuis
2024-06-18T12:24:18Z

On 13.06.24 13:34, Laurent Pinchart wrote:

> On Thu, Jun 13, 2024 at 10:34:17AM +0200, Thorsten Leemhuis wrote:
>
>> I'd like to make the language somewhat stronger.
>>
>> """Handle mainline regressions that recently made it into a proper
>> mainline, stable, or longterm release (either directly or via backport)
>> with an even higher priority and try to fix them as fast as possible.
>> [...] Aim hard to mainline a fix by Sunday after the next, if the
>
> Are we really telling people, some of them contributing in their spare
> time, that they have to work during weekends ?

To clarify: I'm not asking for that at all. The aim for Sunday is only
here because Linus usually releases new -rc's on Sunday evenings, which
quite a few people seem to use. So from the regressions point of view
it's better to flush fixes to Linus late in the week (say on Friday --
or if you want on Sat or Sun, which some subsystem do), and not on a
Monday, as people that use -rcs otherwise will run into the regression
for yet another week -- and sometimes report it again, when the fix was
just mainlined.

What wording can avoid this? "By the end of the (current/next) week"
maybe? In business context that afaik usually mean Fridays, but I'm not
a native speaker, so might be wrong there.

Ciao, Thorsten