Re: Requesting MFC's

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_at_ CC'd so they can be informed of the request
> - Have maintainer-approval ? re_at_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.
> 
>> Thanks in advance,
>>
>> -Matthew
>> _______________________________________________
>> freebsd-current_at_freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
> 
> 
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
> 

RE_at_ 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

-- 
Allan Jude