Date: Wed, 15 Nov 2023 18:38:57 +1100 From: matti k <mattik@gwsit.com.au> To: Glen Barber <gjb@freebsd.org> Cc: FreeBSD Release Engineering Team <re@freebsd.org>, freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: [HEADS-UP] Quick update to 14.0-RELEASE schedule Message-ID: <20231115183857.2c728fa5@ws1.wobblyboot.net> In-Reply-To: <20231115045231.GN1307@FreeBSD.org> References: <20231114203654.GB52320@FreeBSD.org> <ZVQNtKYYbf1OYu9O@doctor.nl2k.ab.ca> <20231115022701.GM1307@FreeBSD.org> <ZVQ2n1UDGJtIpW3y@doctor.nl2k.ab.ca> <20231115045231.GN1307@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 15 Nov 2023 04:52:31 +0000 Glen Barber <gjb@freebsd.org> wrote: > > > Ok. I do not know what exactly is your point, but releases are > > > never official until there is a PGP-signed email sent. The email > > > is intended for the general public of consumers of official > > > releases, not "yeah, but"s. > > > > That does not say that the freebsd-update bits will not change *until* > the official release announcement has been sent. > > In my past 15 years involved in the Project, I think we have been very > clear on that. > > A RELEASE IS NOT FINAL UNTIL THE PGP-SIGNED ANNOUNCEMENT IS SENT. > > I mean, c'mon, dude. > > We really, seriously, for all intents and purposes, cannot be any more > clear than that. > > So, yes, *IF* an update necessitates a new freebsd-update build, what > you are running is *NOT* official. > > For at least 15 years, we have all said the same entire thing. Here I have been tracking 14.0 release candidates Reminds me of when slashdot would announce a new release days before it was actually released and then someone would remind them of that I am using an Australian mirror so will probably need to wait an extra day to be on the safe side :-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20231115183857.2c728fa5>