[Ksummit-discuss] [MAINTAINER SUMMIT] Stable trees and release time

Sasha Levin Alexander.Levin at microsoft.com
Wed Sep 5 15:00:46 UTC 2018


On Wed, Sep 05, 2018 at 03:50:29PM +0100, Mark Brown wrote:
>On Wed, Sep 05, 2018 at 02:27:29PM +0000, Sasha Levin wrote:
>> On Wed, Sep 05, 2018 at 02:16:43PM +0100, Mark Brown wrote:
>
>> >It's not just maintainers any more - in particular we've got Sasha's
>> >neural net thing picking patches as well and it's substantially more
>> >trigger happy than at least I am.  People do get a chance to review what
>> >it's picking but that's different to maintainers picking things.
>
>> What can I do to make the process better?
>
>> I tried giving longer review periods, I tried sending emails right when
>> the patch is merged upstream instead of weeks later and I tried actively
>> pursuing some maintainers for explicit Acks. None of which seemed to
>> make anyone happier.
>
>Honestly the whole thing just gives me a bit of anxiety.  I'd say most
>of the patches my thinking is "it's *probably* fine" and it's rare for
>me to think "Oh, I missed that important patch!".  As you know I do
>sometimes actively push back on things.  On balance it mostly doesn't
>break things though and I'm not sure what can be improved process wise
>here, a lot of it is fundamentally that if I thought it was clearly good
>for stable I'd have flagged it already.

Indeed. Some maintainers do a better job than others with tagging things
for Stable, so to them it seems like AUTOSEL patches are just noise, but
for other maintainers they basically do all the job for them.


--
Thanks,
Sasha


More information about the Ksummit-discuss mailing list