Date: Fri, 31 Dec 2021 08:17:13 -0800 From: Mark Millard via dev-commits-src-main <dev-commits-src-main@freebsd.org> To: Kyle Evans <kevans@FreeBSD.org> Cc: dev-commits-src-main@freebsd.org Subject: Re: git: e2650af157bc - main - Make CPU_SET macros compliant with other implementations Message-ID: <A3FF34DF-3035-491B-9B91-218EAC261FE4@yahoo.com>
index | next in thread | raw e-mail
From: Kyle Evans <kevans_at_freebsd.org> wrote on Date: Fri, 31 Dec 2021 09:37:16 -0600 : > . . . > This is a mindset that we all take, but we really need to work towards > improving. Once we're watching fallout logs on the official builders, > we've already lost. This is the kind of thing that helps promote the > idea that -CURRENT isn't stable enough for production uses: Hmm. Quoting: https://www.freebsd.org/where/ QUOTE If you are interested in a purely experimental snapshot release of FreeBSD-CURRENT (AKA 14.0-CURRENT), aimed at developers and bleeding-edge testers only, then please see the FreeBSD Snapshot Releases page. END QUOTE I thought that FreeBSD avoided promoting -CURRENT for production uses. > we start > accepting that we can be a little more lenient on identifying > ports-breaking changes because it's -CURRENT and we lose a fraction of > the ports tree because we've only sniped off individual ports as they > come up. > . . . === Mark Millard marklmi at yahoo.comhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A3FF34DF-3035-491B-9B91-218EAC261FE4>