Date: Sat, 2 Nov 2019 16:18:29 +0000 From: Glen Barber <gjb@freebsd.org> To: "Sergey A. Osokin" <osa@freebsd.org> Cc: freebsd-stable@freebsd.org, FreeBSD Release Engineering Team <re@freebsd.org> Subject: Re: 12.1-RELEASE schedule update Message-ID: <20191102161829.GE5599@FreeBSD.org> In-Reply-To: <20191102141250.GA17205@FreeBSD.org> References: <20191025000552.GF51072@FreeBSD.org> <20191101134418.GW12076@FreeBSD.org> <20191101145250.GR1424@FreeBSD.org> <20191102141250.GA17205@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--r7U+bLA8boMOj+mD
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
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:
> > >=20
> > > - 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)
> >=20
> > 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.)
>=20
> Actually we have one, graphics/drm-kmod, and it depends on the following =
one:
>=20
> .elif ${OSVERSION} >=3D 1200058 && ${OSVERSION} < 1300000
> RUN_DEPENDS=3D ${KMODDIR}/drm.ko:graphics/drm-fbsd12.0-kmod
> ...
>=20
> 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 well.
>=20
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.)
> > > Also, since this is repeatable thing for every upcoming release
> > > we can add this point to the check list and release scheduling.
> >=20
> > Yes, good idea. Just let us know how you want to proceed, and we can
> > add a note to the documentation.
>=20
> I mean I believe we should that (create a new port, update the meta-port,
> etc.) in advance, in the beginning of the first phase of release cycle.
>=20
This seems like a reasonable approach.
Glen
--r7U+bLA8boMOj+mD
Content-Type: application/pgp-signature; name="signature.asc"
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAl29rFUACgkQAxRYpUeP
4pPC/g/9FSyy6VkmaujmM82mkBmRiB1waeiv4I7R3jo/EGJj2aOezE53xdQVF4PK
rOv722U8fo2Ro+1RQqHNgO/K77ewuIJllkaONnHcLUauOnlSNFrc1tCAE+baMORn
39nskVNWA22dvURM6vUZP9toNZyxcFlAlDLsQN6oj/QQDAqXlSB+2QiQeSaH1Enj
10kFZZUi/QOGeJiyUEWnpxSbfa3x4eFh3g5pxRCQ4iRh/lcWAaAER8U6qmazbobD
W5MB6o/D3uSRqBUIRNbr+GJEzoyXyBTLW3oxvwzNFyaV9T9lfJpz9XJMhzKogMvC
PGAnjw4slBFSJMigp8VmkbMh+5LfcQbI6+8Y/RGXjXRGgbOS1H4oliSrjcjmvPju
vaV82t3ogPBXYjvuKnDGvKHx/wpVf8flNZSPFq1uJgffhtQ5DMiPwlTh0ePlX3Ve
ULHLLb5fiHv4MpzEZupXoFw/Ly1ILDg0IxVB0QwJ0NdLVMs68RMV3VxT1XeA8R2g
Cmqh7plaA8MF6di4PmWgQlFfzkmB2A2i+8do+8Bj/YxLi2OBZERchkBDOK/Cp3GO
P2tCMZYwNWd3+V4oO55yZd7gY1V/qH1FCB4H7WiUBREp4p2NIlaW69uNBhzo9CHV
YlnK0R7mvMCPVVdnKZsWlUpaE3V3SVP7KNMfjicu3aTxgB7ow28=
=XSrM
-----END PGP SIGNATURE-----
--r7U+bLA8boMOj+mD--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191102161829.GE5599>