The MFC process...

[Warren Block]

On Tue, 17 Jul 2012, Eitan Adler wrote:

> On 17 July 2012 09:28, Warren Block <wblock at wonkity.com> wrote:
>> On Tue, 17 Jul 2012, Eitan Adler wrote:
>>
>>> On 17 July 2012 05:50, David Magda <dmagda at ee.ryerson.ca> wrote:
>>>>
>>>> On Tue, July 17, 2012 02:10, Eitan Adler wrote:
>>>>>
>>>>> Of interest to me: if it could be limited to just the commits I made
>>>>> and optionally show me the log message and diff it would be very
>>>>> helpful.
>>>>>
>>>>> On a general note: be careful with any level of automation with this
>>>>> script though. Sometimes there are good reasons that a commit wasn't
>>>>> MFCed.
>>>
>>>
>>>
>>>> A lot of messages have a "MFC after" note on them, so the the developer/s
>>>> in question already know which commits are good candidates for bringing
>>>> over to STABLE. It may simply be that they could use a reminder on them.
>>>
>>>
>>> Just to add: developers get an automated email at the "MFC after" time
>>> reminding them to MFC.
>>
>>
>> But only once.  It would be nice if it was like PR notifications, once a
>> week.
>
> Please no! If this is the case, it should be an option.

I don't expect it to happen.  But right now, there's only the initial 
mail that the MFC is due, and no reminder afterwards.  We have the open 
PR mails once-weekly; MFCs are at least as important.

Come to think of it, entering PRs for past-due MFCs could be a way to do 
that with the existing systems.