Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 4 Feb 2016 01:44:13 -0500
From:      Allan Jude <allanjude@freebsd.org>
To:        freebsd-current@freebsd.org
Subject:   Re: Requesting MFC's
Message-ID:  <56B2F33D.2060106@freebsd.org>
In-Reply-To: <56B2EC93.9020409@FreeBSD.org>
References:  <56B2B854.2030904@shrew.net> <56B2EC93.9020409@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--KmqkCWndghxVUoB3l6KRC0FLIdDTVfscE
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

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 ha=
ve
>> been required to build a working firewall in some cases. All are relat=
ed
>> to problems that were fixed in HEAD, but never MFC'd ...
>>
>> https://svnweb.freebsd.org/base?view=3Drevision&revision=3D264915
>> https://svnweb.freebsd.org/base?view=3Drevision&revision=3D272695
>> https://svnweb.freebsd.org/base?view=3Drevision&revision=3D288529
>=20
> 1) Create an issue in Bugzilla for it
>   a) Assigned to original committer
>   b) Set mfc-stableX flag to?
>=20
> Committer can then set mfc-stableX flag to + when done, or set it to -
> with comment about why not/invalid/inappropriate
>=20
> If a branch is in feature freeze, issues should either:
>=20
> - 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
>=20
> This is also the recommended method for changes that already have
> bugzilla issues created for them.
>=20
>> Thanks in advance,
>>
>> -Matthew
>> _______________________________________________
>> freebsd-current@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.=
org"
>=20
>=20
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o=
rg"
>=20

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

--=20
Allan Jude


--KmqkCWndghxVUoB3l6KRC0FLIdDTVfscE
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQIcBAEBAgAGBQJWsvNBAAoJEBmVNT4SmAt+6rQP/0u9gkE20f05RJK9hkj6z4Mg
LZjyxNH0OVa0wHseZf9RGICQIohK5htJ8PqmAOTl9YW81DHdpzmnsdBWAY2H540n
20uWS84Ovrma+5jr5TRo2mpIO6Mg0IFbZxKi71Y9erRPZFwUpDRfKue84y4wnju4
epvFCgaiRlMIJ9YRSTLdVsiXtx8SieQQhM5ZeBHtKGDlVh+ny0FuQFJ5JXIALYDY
1dE1t21R9GBsGcWVieuSfD/H4Kb56U7i9ED9TIXoqc5NSjhHfdLRDF8zi7DBHVtN
3L8s2y7ElJEg6MH1LLMSwD7hbXcmsY+vyC8qjYF6xRClKYg/5vXmPz06m+3soesR
TRSAwrZaWPQGfC6FNKyEDDaW2s+CgnxJ68+ugwy02pHQ/kphNOIXNvbmyf3M7yuX
Eim2BMLOBgrOVHCaYR7rcddYPddZ9GzZbHLbZF4UZ+vdxj3BW7nfzZl91qRZOjDb
vj49BHGaTQD8XK7rMyT9sRzIZ7I+IrMdilDptwXXTGoOrMbPtMPHD0aSBsQdWZgA
iz6fmsJ/6eOM9mG41r7zhdYdlDF+QF95qBCPoP07dliBX0k9GVthu02J5GJkf689
v9+UDi2Z1eaAlhq27sOdS+KRwfVOU5EGjc+qaVJ14tTaOatDtJzf+L02IMPiRfEd
wPfzyzcoTiuQaUKKs5XG
=js8E
-----END PGP SIGNATURE-----

--KmqkCWndghxVUoB3l6KRC0FLIdDTVfscE--



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