[Mesa-dev] [RFC] Mesa 9.2 and release process changes
Ian Romanick
idr at freedesktop.org
Sun Jul 21 22:51:31 PDT 2013
On 07/19/2013 10:54 AM, Tom Stellard wrote:
> On Fri, Jul 19, 2013 at 10:42:42AM -0700, Kenneth Graunke wrote:
>> On 07/10/2013 04:38 PM, Ian Romanick wrote:
>> [snip]
>>> Could we just change our "Mark the patch with 'NOTE: ...'" policy with
>>> "To have the patch automatically included in the stable tree, add the tag
>>> Cc: mesa-stable at lists.freedesktop.org
>>>
>>> in the sign-off area..." ?
>>
>> This loses a bit of information, sadly.
>>
>> These two are interchangeable:
>> NOTE: This is a candidate for the stable branches.
>> Cc: mesa-stable at lists.freedesktop.org
>>
>> But what about:
>> NOTE: This is a candidate for the 9.2 branch.
>> (but not the 9.1 branch, or 9.0 branch...)
>>
>> What then?
>
> Is there any reason why CC: mesa-stable at lists.freedesktop.org is
> preferable over the old NOTE: This is a candidate ...
> annotation?
You can nominate a branch after it has been pushed to master, and having
two mechanisms for the same thing makes more work for the stable maintainer.
It also means that you can reply to a patch (after it has landed on
master) with NAK of stable... and that won't get lost.
> -Tom
More information about the mesa-dev
mailing list