From nobody Mon May 1 18:28:46 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Q9BYt1Zt2z48r3n for ; Mon, 1 May 2023 18:29:06 +0000 (UTC) (envelope-from jon@xyinn.org) Received: from mail-4323.proton.ch (mail-4323.proton.ch [185.70.43.23]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "protonmail.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q9BYs6J3xz4GYQ; Mon, 1 May 2023 18:29:05 +0000 (UTC) (envelope-from jon@xyinn.org) Authentication-Results: mx1.freebsd.org; none Date: Mon, 01 May 2023 18:28:46 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=xyinn.org; s=protonmail; t=1682965743; x=1683224943; bh=dsPCnApY9CsmM7pE37yxwv3EjIuynoavjYNnLFBFJ+E=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=dbT9JKakgxrmXMmv3WwjN4LWWG2YFHumy2MDUQFSaS02tiaPgRwNs8fsfjkK8yQB4 TyKduRERXcCiC0n3e716ZnMvCrp0hb8hpnWofEh3GBQX/2SvXKhS2AE9SvHzcYktoT xfJkWtuB2Sg44hPrHitiQI3vPfCGQCkPuY/i+Bj5VlwRJCgFHjFhixfVPo4irvIcx+ R8Oi2c2XEB04pdlEX23ubC+A7hTPDgOShw3Y5NrGNHWMbLQUe6NdfBrKwxkdIJIuNk XAqGKvN/HNaIgLQ/o9fiy1GakqKIJw8/gAFuUOVP2sA9yZRKJMapNDCIAxIL+gJ75U rPjdCePby0pJQ== To: Glen Barber From: Jonathan Vasquez Cc: freebsd-arch@freebsd.org, freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, FreeBSD Release Engineering Team , FreeBSD Security Team Subject: Re: Delay in 14.0-RELEASE cycle and blocking items Message-ID: <-KbYxRwo9K3JhPBb9oSHhTb_uV3LMt5jkPyzykT6NU01XBkT9VTG0Ju8BISMSKZSh82s0r3iDZk2eDs49weh1uUOAdYjp7SOKTG768uk46k=@xyinn.org> In-Reply-To: <20230501181449.GJ1219@FreeBSD.org> References: <20230501181449.GJ1219@FreeBSD.org> Feedback-ID: 12351801:user:proton List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4Q9BYs6J3xz4GYQ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:62371, ipnet:185.70.43.0/24, country:CH] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Thanks for the update Glen. Yup that makes sense. Given that stable/14 will be supported for years to c= ome, it's better to take a little bit longer and make sure we get it right. Jonathan Vasquez PGP: 34DA 858C 1447 509E C77A D49F FB85 90B7 C4CA 5279 Sent with ProtonMail Secure Email ------- Original Message ------- On Monday, May 1st, 2023 at 14:14, Glen Barber wrote: > According to the 14.0-RELEASE schedule, the code slush in main and the > freeze to the KBI for 14.0 was scheduled for April 25, 2023. As some of > you may have noticed, that did not happen. >=20 > First, and most importantly for 14.0, is the status of the OpenSSL > update to version 3. This in itself is reason to delay the schedule > until some tangible progress has been made. Yes, some have expressed > interest in helping in this area, however at this moment, this is the > key blocker. >=20 > Second is the status of the branch and how it pertains to the recent > upstream merge from OpenZFS. Although block_cloning is disabled by > default, there have been other regressions discovered (and fixed), but > as a whole, I do not feel that we have a solid understanding of the > regressions about which we do not know. >=20 > 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 > A more up-to-date schedule for the 14.0 release will be published in the > near future, though nothing is yet set in stone. >=20 > Thank you for your patience, and for any help in getting us through > these outstanding items. >=20 > Glen > On behalf of: re@