Date: Mon, 31 Jan 2022 14:49:49 +1000 From: George Michaelson <ggm@algebras.org> To: Kyle Evans <kevans@freebsd.org> Cc: FreeBSD Stable <freebsd-stable@freebsd.org>, FreeBSD Security Team <secteam@freebsd.org> Subject: Re: Why is freebsd-update telling me 13.0 is EOL? 13.1 isn't visibly even in beta. Message-ID: <CAKr6gn3BNLLFsB-DLvis4nrc%2BVjC-De-r=fxF4nmMsZpMv3n5A@mail.gmail.com> In-Reply-To: <CACNAnaHgx_SK7_1iXrxE=epF%2BKPY6bViW-0JpEh-E17Fctc%2BNQ@mail.gmail.com> References: <CAKr6gn3C34YGZyfdQHr9R5pkP_CnVetiH0h01R_hXWABbi4YVg@mail.gmail.com> <CACNAnaHgx_SK7_1iXrxE=epF%2BKPY6bViW-0JpEh-E17Fctc%2BNQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Hi, > > The freebsd-update metadata contains an EoL date that is (presumably) > solely for displaying this message. Right now, we don't know an exact > EoL date of most minor releases until the next minor release schedule > is published, so a projected EoL date is included and updated once the > new release is published. > > I'm trying to get this changed to use the branch EoL before we know > when the exact EoL is; the working theory is that nobody uses this > metadata to actually gauge a minor release's EoL, so we'd be better > off setting it to the branch-end until we know better rather than > alerting people this way. > > Thanks, > > Kyle Evans Thanks Kyle. The change sounds sensible. -G
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKr6gn3BNLLFsB-DLvis4nrc%2BVjC-De-r=fxF4nmMsZpMv3n5A>