Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 1 Feb 2022 07:19:33 +0000
From:      Graham Perrin <grahamperrin@gmail.com>
To:        Kyle Evans <kevans@freebsd.org>
Cc:        questions@freebsd.org
Subject:   End-of-life notice adjustments
Message-ID:  <8777a3a4-1b72-10ee-7986-2a902239edd4@gmail.com>
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
Re: FreeBSD 13.0 Coming to An End... Already?

On 30/01/2022 15:55, Kyle Evans wrote:

>
> … 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
> instead initially populate it with the branch EoL and adjust it to be
> closer once the new schedule is released -- in theory, nobody uses
> this for other reasons and they just won't notice as long as we get it
> set right closer to EoL.
>
> Thanks,
>
> Kyle Evans


Kyle and colleagues: if not already on your radar, maybe also some 
adjustment for releng/12.2.

Please see, for example, the notice that's quoted here:

<https://forums.freebsd.org/posts/553832>;

As always, thank you.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8777a3a4-1b72-10ee-7986-2a902239edd4>