Date: Wed, 15 Nov 2023 08:39:39 -0800 From: John Baldwin <jhb@FreeBSD.org> To: Glen Barber <gjb@freebsd.org>, The Doctor <doctor@doctor.nl2k.ab.ca> 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: <e86e5e6f-e986-410f-bdb2-8d4273f2815e@FreeBSD.org> 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 11/14/23 8:52 PM, Glen Barber wrote: > On Tue, Nov 14, 2023 at 08:10:23PM -0700, The Doctor wrote: >> On Wed, Nov 15, 2023 at 02:27:01AM +0000, Glen Barber wrote: >>> On Tue, Nov 14, 2023 at 05:15:48PM -0700, The Doctor wrote: >>>> On Tue, Nov 14, 2023 at 08:36:54PM +0000, Glen Barber wrote: >>>>> We are still waiting for a few (non-critical) things to complete before >>>>> the announcement of 14.0-RELEASE will be ready. >>>>> >>>>> It should only be another day or so before these things complete. >>>>> >>>>> Thank you for your understanding. >>>>> >>>> >>>> I always just installed my copy. >>>> >>> >>> 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. >>> >> >> Howver if you do a freebsd-update upgrade, you can upgrade. >> >> Is that suppose to happen? >> > > 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. Yes, but, if at this point we had to rebuild, it would have to be 14.0.1 or something (which we have done a few times in the past). It would be too confusing otherwise once the bits are built and published (where published means "uploaded to our CDN"). It is the 14.0 release bits, the only question is if for some reason we had a dire emergency that meant we had to pull it at the last minute and publish different bits (under a different release name). Realistically, once the bits are available, we can't prevent people from using them, it's just at their own risk to do so until the project says "yes, we believe these are good". Granted, they are under the same risk if they are still running the last RC. The best way to minimize that risk going forward is to add more automation of testing/CI to go along with the process of building release bits so that the build artifacts from the release build run through CI and are only published if the CI is green as that would give us greater confidence of "we believe these are good" before they are uploaded for publishing. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e86e5e6f-e986-410f-bdb2-8d4273f2815e>