Date: Wed, 3 May 2023 20:20:08 +0200 From: Rainer Duffner <rainer@ultra-secure.de> To: Glen Barber <gjb@FreeBSD.org> Cc: Mark Millard via freebsd-current <freebsd-current@freebsd.org> Subject: Re: Delay in 14.0-RELEASE cycle and blocking items Message-ID: <4CA4995E-4299-4083-ADA7-90397DFE0299@ultra-secure.de> In-Reply-To: <20230503162714.GN1219@FreeBSD.org> References: <20230501181449.GJ1219@FreeBSD.org> <ZFIS5UXhimT6gfwq@FreeBSD.org> <20230503162714.GN1219@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Am 03.05.2023 um 18:27 schrieb Glen Barber <gjb@FreeBSD.org>: >=20 > On Wed, May 03, 2023 at 07:53:09AM +0000, Alexey Dokuchaev wrote: >> On Mon, May 01, 2023 at 06:14:49PM +0000, Glen Barber wrote: >>> ... >>> There is no feasible way we are going to make the branch point of >>> stable/14 in time, with that scheduled for May 12, 2023 with the = above >>> points. That said, this is not an all-inclusive list, but the more >>> major items on our radar at the moment. >>=20 >> Does this delay mean we might get Clang 16 in the base? >>=20 >=20 > Well, the delay really means we do not currently have OpenSSL 3 in = base. >=20 > Glen >=20 I cannot help with this, of course. But out of interest: what are the problems? There was a post on the haproxy mailing-list a while back, linking to = some github issue and from what I understood, there are huge = performance-problems in there. Rainer=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CA4995E-4299-4083-ADA7-90397DFE0299>