Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 4 Feb 2016 17:58:38 +1100
From:      Kubilay Kocak <koobs@FreeBSD.org>
To:        Allan Jude <allanjude@freebsd.org>, freebsd-current@freebsd.org
Subject:   Re: Requesting MFC's
Message-ID:  <56B2F69E.1000404@FreeBSD.org>
In-Reply-To: <56B2F33D.2060106@freebsd.org>
References:  <56B2B854.2030904@shrew.net> <56B2EC93.9020409@FreeBSD.org> <56B2F33D.2060106@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 4/02/2016 5:44 PM, Allan Jude wrote:
> On 2016-02-04 01:15, Kubilay Kocak wrote:
>> On 4/02/2016 1:32 PM, Matthew Grooms wrote:
>>> All,
>>>
>>> What is the correct way to request that patches be committed to STABLE?
>>> In particular, I'd really like to see these in 10.3-RELEASE as they have
>>> been required to build a working firewall in some cases. All are related
>>> to problems that were fixed in HEAD, but never MFC'd ...
>>>
>>> https://svnweb.freebsd.org/base?view=revision&revision=264915
>>> https://svnweb.freebsd.org/base?view=revision&revision=272695
>>> https://svnweb.freebsd.org/base?view=revision&revision=288529
>>
>> 1) Create an issue in Bugzilla for it
>>   a) Assigned to original committer
>>   b) Set mfc-stableX flag to?
>>
>> Committer can then set mfc-stableX flag to + when done, or set it to -
>> with comment about why not/invalid/inappropriate
>>
>> If a branch is in feature freeze, issues should either:
>>
>> - Have re@ CC'd so they can be informed of the request
>> - Have maintainer-approval ? re@FreeBSD.org set so that the release
>> engineering team can approve/deny changes
>>
>> This is also the recommended method for changes that already have
>> bugzilla issues created for them.
>>

> 
> RE@ has a specific procedure for requesting approval for an MFC during a
> freeze: https://wiki.freebsd.org/Releng/ChangeRequestGuidelines
> I would imagine they prefer not to be added to bugzilla issues until a
> committer decides it is worth MFCing something
> 

Yes, sorry.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56B2F69E.1000404>