Date: Wed, 2 Nov 2022 11:27:23 -0400 From: Michael Sierchio <kudzu@tenebras.com> To: Kyle Evans <kevans@freebsd.org> Cc: Arthur Chance <freebsd@qeng-ho.org>, FreeBSD-Questions <freebsd-questions@freebsd.org>, FreeBSD Security Team <secteam@freebsd.org> Subject: Re: 12.3 EOL warning? Message-ID: <CAHu1Y70Scs5fn4mOTs3S4E9972_rm=F%2B4Zt816TmjhQqcPTvLA@mail.gmail.com> In-Reply-To: <CACNAnaGF4rcqs-VU69azE5ehUydASHiraSt40vbDUhZPF=q1Tw@mail.gmail.com> References: <eb7434d5-a72b-7b35-b8e6-063e6f43f04c@qeng-ho.org> <CACNAnaGF4rcqs-VU69azE5ehUydASHiraSt40vbDUhZPF=q1Tw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--00000000000054e2a105ec7e7c5a Content-Type: text/plain; charset="UTF-8" On Wed, Nov 2, 2022 at 11:22 AM Kyle Evans <kevans@freebsd.org> wrote: > On Wed, Nov 2, 2022 at 3:15 AM Arthur Chance <freebsd@qeng-ho.org> wrote: > > > > Patching a 12.3 system to deal with the latest security advisory I got > > > > WARNING: FreeBSD 12.3-RELEASE-p6 is approaching its End-of-Life date. > > It is strongly recommended that you upgrade to a newer > > release within the next 2 months. > > > freebsd-update metadata includes the EoL date, which we don't > typically know when a release is cut since it depends on an > undetermined schedule for the next release. I asked secteam@ a while > back if we could just specify the end of branch as the EoL for new > releases until re@ confirms a schedule to tune that back with (which > makes sense, since it *will* be the end of the branch if all of re@ > decides that a nice prolonged beach vacation sounds more fun). I don't > know that that went anywhere, but we really need to do something to > avoid this kind of question coming up because we get it wrong more > often than not. CC secteam@. > Updating to 12.3-RELEASE-p7 quiets the warning. --00000000000054e2a105ec7e7c5a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">= <div dir=3D"ltr" class=3D"gmail_attr">On Wed, Nov 2, 2022 at 11:22 AM Kyle = Evans <<a href=3D"mailto:kevans@freebsd.org">kevans@freebsd.org</a>> = wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0= px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Wed, N= ov 2, 2022 at 3:15 AM Arthur Chance <<a href=3D"mailto:freebsd@qeng-ho.o= rg" target=3D"_blank">freebsd@qeng-ho.org</a>> wrote:<br> ><br> > Patching a 12.3 system to deal with the latest security advisory I got= <br> ><br> > WARNING: FreeBSD 12.3-RELEASE-p6 is approaching its End-of-Life date.<= br> > It is strongly recommended that you upgrade to a newer<br> > release within the next 2 months.<br><br> <br> freebsd-update metadata includes the EoL date, which we don't<br> typically know when a release is cut since it depends on an<br> undetermined schedule for the next release. I asked secteam@ a while<br> back if we could just specify the end of branch as the EoL for new<br> releases until re@ confirms a schedule to tune that back with (which<br> makes sense, since it *will* be the end of the branch if all of re@<br> decides that a nice prolonged beach vacation sounds more fun). I don't<= br> know that that went anywhere, but we really need to do something to<br> avoid this kind of question coming up because we get it wrong more<br> often than not. CC secteam@.<br></blockquote><div><br></div><div>Updating t= o 12.3-RELEASE-p7 quiets the warning.</div><div>=C2=A0</div></div></div> --00000000000054e2a105ec7e7c5a--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHu1Y70Scs5fn4mOTs3S4E9972_rm=F%2B4Zt816TmjhQqcPTvLA>