Date: Sat, 2 Nov 2019 18:31:21 +0000 From: Glen Barber <gjb@freebsd.org> To: Warner Losh <imp@bsdimp.com> Cc: "Sergey A. Osokin" <osa@freebsd.org>, FreeBSD Release Engineering Team <re@freebsd.org>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: 12.1-RELEASE schedule update Message-ID: <20191102183121.GX1424@FreeBSD.org> In-Reply-To: <CANCZdfo5H9MtaO_Dt7gHnfiL9SC9VFj34xmPLeTTydFA4KTL6Q@mail.gmail.com> References: <20191025000552.GF51072@FreeBSD.org> <20191101134418.GW12076@FreeBSD.org> <20191101145250.GR1424@FreeBSD.org> <20191102141250.GA17205@FreeBSD.org> <20191102161829.GE5599@FreeBSD.org> <CANCZdfo5H9MtaO_Dt7gHnfiL9SC9VFj34xmPLeTTydFA4KTL6Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--qRqofxetdBO9L27H
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sat, Nov 02, 2019 at 12:14:05PM -0600, Warner Losh wrote:
> On Sat, Nov 2, 2019 at 10:20 AM Glen Barber <gjb@freebsd.org> wrote:
>=20
> > On Sat, Nov 02, 2019 at 02:12:50PM +0000, Sergey A. Osokin wrote:
> > > On Fri, Nov 01, 2019 at 02:52:50PM +0000, Glen Barber wrote:
> > > > On Fri, Nov 01, 2019 at 01:44:18PM +0000, Sergey A. Osokin wrote:
> > > > > At the moment we have graphics/drm-fbsd12.0-kmod port for 12.0.
> > > > > I hope in most cases it's enough for RELENG_12 branch, however
> > > > > just to avoid a potential confusion I see the following options
> > > > > we can do:
> > > > >
> > > > > - create a new port for 12.1 only
> > > > > - rename the existing port to drm-fbsd12-kmod
> > > > > - rename the existing port to drm-fbsd12.1-kmod (in case of 12.0 =
EoL)
> > > >
> > > > What about using the meta-port and keying off of OSVERSION?
> > (Personally
> > > > I have no real preference either way, nor with any of the solutions=
you
> > > > propose above.)
> > >
> > > Actually we have one, graphics/drm-kmod, and it depends on the follow=
ing
> > one:
> > >
> > > .elif ${OSVERSION} >=3D 1200058 && ${OSVERSION} < 1300000
> > > RUN_DEPENDS=3D ${KMODDIR}/drm.ko:graphics/drm-fbsd12.0-kmod
> > > ...
> > >
> > > So, in case we don't expect an API/ABI changes in 12.x branch we can
> > > just rename it to drm-fbsd12-kmod, or create a specific version of
> > > the port for 12.1 - drm-fbsd12.1-kmod and update the meta-port as wel=
l.
> > >
> >
> > We should never expect this type of ABI/KBI breakage along a stable
> > branch. (That is our definition of "stable", technically, but sometimes
> > there are unexpected breakages that occasionally go undetected.)
> >
>=20
> The KPIs that drm depends on are quite specific and weird and aren't part
> of the set we guarantee (and we can't do what drm needs to do with only t=
he
> 'safe' ones). It's not much different than virtual box which also has this
> issue frequently because it too falls into that category.
>=20
Agreed. (FWIW, I specifically made sure the virtualbox-ose-additions
did not cause system crashes for 12.1.)
> > > > Also, since this is repeatable thing for every upcoming release
> > > > > we can add this point to the check list and release scheduling.
> > > >
> > > > Yes, good idea. Just let us know how you want to proceed, and we c=
an
> > > > add a note to the documentation.
> > >
> > > I mean I believe we should that (create a new port, update the meta-p=
ort,
> > > etc.) in advance, in the beginning of the first phase of release cycl=
e.
> > >
> >
> > This seems like a reasonable approach.
> >
>=20
> How do we get packages from the new port into the release so that users
> don't install the 12.0 port by mistake?
>=20
It just needs to be merged to the 2019Q4 ports branch. For the package
available on the dvd, it is unfortunately too late, but only the
graphics/drm-legacy-kmod and graphics/drm-stable-kmod packages are on
the dvd by default anyway. In other words, the meta-port is not
included, but once a commit is merged to the 2019Q4 branch and the
upstream binary packages are rebuilt, they will be available by default.
Glen
--qRqofxetdBO9L27H
Content-Type: application/pgp-signature; name="signature.asc"
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAl29y3UACgkQAxRYpUeP
4pMmXA//Vxp4OCvoEa4OhOe5jFRKCxEGnPEeZpIpAZrJ8/InqpByAx7s+vU6X5Hm
vqJVV7nDNbeXaw19sVkR9zTFmE9Tc+R0lrQTt7ZjLtp+XyVakMd9kmXYI47RXOX1
L3B9B1vcTLdHFp3n2DEzwhVPwmxSVeCW42O7IwKjENQjzrjtz+oXGMzXjhnTThUe
cBBCHMtreB1lrtYV3BaH1zY+f7apQ1OxRx5F2WO1D3qJyc1zi8dg9mz/ctzXecbw
rFtoxoSdlDTgFVOSdq/A3GrOCWPPdMWOhyRHS3/ciWdB/yg4m+q/XELrRVwrYwWo
cC+XRDy6v5eVkWhorLD1DF7jGlS0ej/m6X69fhF0jmWHxnNMdYEG62QK/aD7iwGl
BntQQ0eyfCFRGKu0YYDmxjZs6J5sXJOrr/CTaJtBZleZfkkTFaKREC5ysavlKgg+
O9YFsnFZFJy7TiWBZgJamD+bsk608yj/oVq28omh5EErerFMNDE682CKvq3oQqOS
Ku148yGxYFCZzGB5pa7hNkyzEQ7ofY2RUk8yvFr1bbt8FxEXVDKSYme8XY22gr7D
TnOShmDV7vuQ/moC517hYz+Is3rtviEAwdodOe4kdDWqIWXkpiSxakrKnuJUMtDq
HLCNdhG31L88bg/2L/wfYMJUKdabsfspyv0owp+E2QtlT3k/JgM=
=yTlu
-----END PGP SIGNATURE-----
--qRqofxetdBO9L27H--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191102183121.GX1424>