From nobody Sun Jan 30 16:28:29 2022 X-Original-To: questions@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 D3F56197CD8A for ; Sun, 30 Jan 2022 16:28:50 +0000 (UTC) (envelope-from 4250.82.1d4d900031a3750.bbead5c7d00a950f250b4cb70716e971@email-od.com) Received: from s1-b0c6.socketlabs.email-od.com (s1-b0c6.socketlabs.email-od.com [142.0.176.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4JmxTY0qJpz4mPM for ; Sun, 30 Jan 2022 16:28:48 +0000 (UTC) (envelope-from 4250.82.1d4d900031a3750.bbead5c7d00a950f250b4cb70716e971@email-od.com) DKIM-Signature: v=1; a=rsa-sha256; d=email-od.com;i=@email-od.com;s=dkim; c=relaxed/relaxed; q=dns/txt; t=1643560129; x=1646152129; h=content-transfer-encoding:content-type:mime-version:references:in-reply-to:message-id:subject:cc:to:from:date:x-thread-info; bh=uRTg1mcVfJlP1bgLsV+6oGSoxIybydFGK1oRBDaQShk=; b=D2yThD0U/nKsIulKopiuXT9D6UEQuozIuiMXP6BBahEQmw47TFZ3umvlLDajsYR0pieEnX7h0a9Binst7zCFkQXAL3lV77OcaFwdNBNGlMh8+vyq9VjkMbfUQiKwvc53SY5TIKQfxeTmvANFAIGDiLymPjruA3xbileoFEaFk9M= X-Thread-Info: NDI1MC4xMi4xZDRkOTAwMDMxYTM3NTAucXVlc3Rpb25zPWZyZWVic2Qub3Jn Received: from r2.h.in.socketlabs.com (r2.h.in.socketlabs.com [142.0.180.12]) by mxsg2.email-od.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Sun, 30 Jan 2022 11:28:31 -0500 Received: from smtp.lan.sohara.org (EMTPY [185.202.17.215]) by r2.h.in.socketlabs.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Sun, 30 Jan 2022 11:28:31 -0500 Received: from [192.168.63.1] (helo=steve.lan.sohara.org) by smtp.lan.sohara.org with smtp (Exim 4.94.2 (FreeBSD)) (envelope-from ) id 1nED41-0008VI-Fy; Sun, 30 Jan 2022 16:28:29 +0000 Date: Sun, 30 Jan 2022 16:28:29 +0000 From: Steve O'Hara-Smith To: Kyle Evans Cc: questions@freebsd.org Subject: Re: FreeBSD 13.0 Coming to An End... Already? Message-Id: <20220130162829.c546d2e55f671cb2e950a854@sohara.org> In-Reply-To: References: <20220130125731.91caded5d25acefd23d067e8@sohara.org> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.0) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4JmxTY0qJpz4mPM X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=email-od.com header.s=dkim header.b=D2yThD0U; dmarc=none; spf=pass (mx1.freebsd.org: domain of 4250.82.1d4d900031a3750.bbead5c7d00a950f250b4cb70716e971@email-od.com designates 142.0.176.198 as permitted sender) smtp.mailfrom=4250.82.1d4d900031a3750.bbead5c7d00a950f250b4cb70716e971@email-od.com X-Spamd-Result: default: False [-1.70 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[email-od.com:s=dkim]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:142.0.176.0/20:c]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[sohara.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[email-od.com:+]; RCPT_COUNT_TWO(0.00)[2]; RWL_MAILSPIKE_EXCELLENT(0.00)[142.0.176.198:from]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MLMMJ_DEST(0.00)[questions]; FORGED_SENDER(0.30)[steve@sohara.org,4250.82.1d4d900031a3750.bbead5c7d00a950f250b4cb70716e971@email-od.com]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:7381, ipnet:142.0.176.0/22, country:US]; FROM_NEQ_ENVFROM(0.00)[steve@sohara.org,4250.82.1d4d900031a3750.bbead5c7d00a950f250b4cb70716e971@email-od.com]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[email-od.com:dkim] X-ThisMailContainsUnwantedMimeParts: N On Sun, 30 Jan 2022 09:55:57 -0600 Kyle Evans wrote: > Correct. The freebsd-update metadata includes the EoL, so it's > initially populated with the projected EoL and gets adjusted when the > next release's schedule is released. I'm trying to see if we can That's about what I thought was going on. > instead initially populate it with the branch EoL and adjust it to be > closer once the new schedule is released -- in theory, nobody uses I like that idea - it's also right for the last one on the branch and in principle any one might be the last for the branch. -- Steve O'Hara-Smith Odds and Ends at http://www.sohara.org/