From nobody Mon May 01 18:14:49 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 4Q9BFX15KGz48qS3; Mon, 1 May 2023 18:14:56 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (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 "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q9BFX0SJcz4BpD; Mon, 1 May 2023 18:14:56 +0000 (UTC) (envelope-from gjb@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1682964896; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type; bh=982sUHCVyS2oRa34lrZYsnJAj5HelSWghZYUY1qthSo=; b=e2uyA5Q6AD9bbISlvsMI0vyfsPzicaOC7XD5E+MKNMw+fJbaWceMZvlzdSje7Fte3zvK0P FrlCBGI5aTy34N3Dz+5wTSFfvK4ynDogYuDHU07+4H7Pe9GLunqGYvuZ8wa+qJFB5y4jZQ AGgXtDITDYY2ipt7MbmFd5D8qPuzQPrlHrq722VREPrjQtFcXK8wHfZW5+AFgs1cVtj8CU /zEVQmHdbUwT7KG2KE8HJtXHJ6rFxo+joUyYMp3wE6WUWz0Q+FZejk4///8wSc9GK+gHov MNMhEr8Ft5tPFvz+42X4K0aJtvoKtFtcM2+CEf+K7Vhgc9D76xyG0wdHlf/Ujw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1682964896; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type; bh=982sUHCVyS2oRa34lrZYsnJAj5HelSWghZYUY1qthSo=; b=ooBppsiqA/6CY/P+1fmTIFw3W2g+8gW2ykyuUczDT6bUBaTrLiwPe1BtbX9XMx/RefFJSD YIYGtL9gJhFcXL13E8xQzFj0ExuMg/PVctVfqKyxLcR4rQ9H5O/2y3MfrAvrQGO9ix9YNo PiLGJXHVlXPmEsbwXpWA3bksTjNwPL4gedhtJ/Ml8WQlUHKoYhXmPbwc0yA5R0JDRT6glF mjKp5kjfVAzK5hc5fJ9fBKwTTTTY/oV6h3/UC79lKfAU7vl3dml0wxo/Hk/rSGFl6Eqr9V JDaZX6gKs+ZlewGC2KUYJ7sfJ/DM6WW75HHBTeNBhQdJ0Emz9KVYqQ9DrnazAg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1682964896; a=rsa-sha256; cv=none; b=Nt/9fSS1IBJon5alsFoswCLb7BHObHOmSLrR3nV+C6xhEq6d2Ss6idHhxCS9YUAuNLzgob I8yyLUI2FYNsTLc7JD3u8OlhqYwLC+Xg34gzjSLVwXqKWAfD094VGfo6/eyGvoAPyd5zlp qyZNnzE6ZzTiEBk+GB5JPLibv5AI9tUA/MBntGBrlg9mL5nLPnfLruni/ClATJVupto0bD LLiHWMCsQzJVm5rEHSpfA8axTMBJVc3E8G1XQ5/OeWb4XR6VwbkUgo++YHinJWTHZEskMG Y7N0OpSrAtriGeIwd0VfjHeKglNE5kiqOzDVztsGAaUU3ntuEj3EvGlG+5+ppg== Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 87671B0E9; Mon, 1 May 2023 18:14:55 +0000 (UTC) (envelope-from gjb@freebsd.org) Date: Mon, 1 May 2023 18:14:49 +0000 From: Glen Barber To: freebsd-arch@freebsd.org, freebsd-hackers@freebsd.org Cc: freebsd-current@freebsd.org, FreeBSD Release Engineering Team , FreeBSD Security Team Subject: Delay in 14.0-RELEASE cycle and blocking items Message-ID: <20230501181449.GJ1219@FreeBSD.org> 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: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="cyV/sMl4KAhiehtf" Content-Disposition: inline X-ThisMailContainsUnwantedMimeParts: N --cyV/sMl4KAhiehtf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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. 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. 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. 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. 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. Thank you for your patience, and for any help in getting us through these outstanding items. Glen On behalf of: re@ --cyV/sMl4KAhiehtf Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAmRQAZkACgkQAxRYpUeP 4pPQJg/8CO1Z12iekJPausELsStIi0rsCxZPtx9wOXAOKWIJmc85ss35UFluPbWy 8iKAciUuHqCTg7GebTPpkbTx/MptAvbO+xFbKfiGPUrRLuLF4DftKvMyaaDWqo7K nUZ5ob3ldLaPkiYGjJ3vayf1HvXTa9bHf8I0eie/fY8fm20Yro00dYGDcr1UoxoQ QPUDJ7hulN11nw6mt/ywHM5gYTe3hT4BphJ+KLu+5tayEvmv7sgFd7F/oXW4BnPo BZsi0jZf49udUxdFpssyzaQsV5fyZYgjeelG/znQ6bQPO9PwE3NJEzTUz19F0MWY lxuJeuyB3iz5ZBEvNLbHXxKjBCTjANN8l2lUU4iQshm1nKIR3SbaTw6P/3L79UwF aP+1OAMpwKT+1xnZRWnrMWmpDEcrWjvXy4aBmpTXobxHT5zpBU1lecKGmpFWpOMp KJEDEEndQlgTZh2KfWE80xIWnnvG7dEkxdIgyHXeYjSrkUqCA8wsZqmV7LOdCFxv rUDjeuhcDQNsgEXMM2e+OTt+TAb7xIagX7cYqTN9ATZjzHcbP65jfBhi7dYF7lhZ Thrj1+u5xzNqc2bbEuZbZBWK0+hp+Z0DoKy/ka3XNguP868+SmsG07KErnLr+KYU j20ZRz5S2iKrmdXtkc2Rn0FY/CUOJievJtIun6dY2tfkUBJNcm0= =aAce -----END PGP SIGNATURE----- --cyV/sMl4KAhiehtf--