From nobody Wed May  3 08:48:10 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 4QB9Zt557Pz4962K
	for <freebsd-current@mlmmj.nyi.freebsd.org>; Wed,  3 May 2023 08:48:22 +0000 (UTC)
	(envelope-from lme@FreeBSD.org)
Received: from mail.0x20.net (mail.0x20.net [46.251.251.56])
	(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 did not present a certificate)
	by mx1.freebsd.org (Postfix) with ESMTPS id 4QB9Zs2s1sz3Cwf
	for <freebsd-current@freebsd.org>; Wed,  3 May 2023 08:48:21 +0000 (UTC)
	(envelope-from lme@FreeBSD.org)
Authentication-Results: mx1.freebsd.org;
	dkim=none;
	spf=softfail (mx1.freebsd.org: 46.251.251.56 is neither permitted nor denied by domain of lme@FreeBSD.org) smtp.mailfrom=lme@FreeBSD.org;
	dmarc=none
Received: from 0x20.net (webs.0x20.net [46.251.251.54])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
	(No client certificate requested)
	(Authenticated sender: lala)
	by mail.0x20.net (Postfix) with ESMTPSA id 6E5461A773C
	for <freebsd-current@freebsd.org>; Wed,  3 May 2023 10:48:10 +0200 (CEST)
List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-current
List-Help: <mailto:freebsd-current+help@freebsd.org>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Subscribe: <mailto:freebsd-current+subscribe@freebsd.org>
List-Unsubscribe: <mailto:freebsd-current+unsubscribe@freebsd.org>
Sender: owner-freebsd-current@freebsd.org
MIME-Version: 1.0
Date: Wed, 03 May 2023 10:48:10 +0200
From: Lars Engels <lme@FreeBSD.org>
To: freebsd-current@freebsd.org
Subject: Re: Delay in 14.0-RELEASE cycle and blocking items
In-Reply-To: <20230501181449.GJ1219@FreeBSD.org>
References: <20230501181449.GJ1219@FreeBSD.org>
Message-ID: <fdfc0a7f78885e34146ad7631717a54d@0x20.net>
X-Sender: lme@FreeBSD.org
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
X-Spamd-Result: default: False [0.70 / 15.00];
	NEURAL_SPAM_LONG(0.99)[0.993];
	NEURAL_HAM_SHORT(-0.93)[-0.934];
	NEURAL_SPAM_MEDIUM(0.74)[0.742];
	MIME_GOOD(-0.10)[text/plain];
	R_DKIM_NA(0.00)[];
	RCVD_COUNT_TWO(0.00)[2];
	MIME_TRACE(0.00)[0:+];
	MLMMJ_DEST(0.00)[freebsd-current@freebsd.org];
	ASN(0.00)[asn:48314, ipnet:46.251.251.0/24, country:DE];
	FROM_EQ_ENVFROM(0.00)[];
	DMARC_NA(0.00)[freebsd.org];
	RCVD_VIA_SMTP_AUTH(0.00)[];
	RCPT_COUNT_ONE(0.00)[1];
	FROM_HAS_DN(0.00)[];
	FREEFALL_USER(0.00)[lme];
	ARC_NA(0.00)[];
	RCVD_TLS_ALL(0.00)[];
	TO_MATCH_ENVRCPT_ALL(0.00)[];
	TO_DN_NONE(0.00)[];
	PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org];
	R_SPF_SOFTFAIL(0.00)[~all];
	TO_DOM_EQ_FROM_DOM(0.00)[]
X-Rspamd-Queue-Id: 4QB9Zs2s1sz3Cwf
X-Spamd-Bar: /
X-ThisMailContainsUnwantedMimeParts: N

Am 2023-05-01 20:14, schrieb Glen Barber:
> 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@


Is there a chance to get pkgbase into 14.0? If not it will take another
X years to have it in 15.0...