Date: Sun, 30 Jan 2022 16:28:29 +0000 From: Steve O'Hara-Smith <steve@sohara.org> To: Kyle Evans <kevans@freebsd.org> Cc: questions@freebsd.org Subject: Re: FreeBSD 13.0 Coming to An End... Already? Message-ID: <20220130162829.c546d2e55f671cb2e950a854@sohara.org> In-Reply-To: <CACNAnaEqw5aKaxiouV-94okA6uCYpoTV3H1QPOWwHqo9zwcjpQ@mail.gmail.com> References: <a45b910e-7291-bf1b-3eb7-dae3c3d49ffd@tinka.africa> <YfXcAMtIUaJCAJ4m@ircbsd.lifeofadishwasher.com> <20220130125731.91caded5d25acefd23d067e8@sohara.org> <CACNAnaEqw5aKaxiouV-94okA6uCYpoTV3H1QPOWwHqo9zwcjpQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 30 Jan 2022 09:55:57 -0600 Kyle Evans <kevans@freebsd.org> 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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220130162829.c546d2e55f671cb2e950a854>