Date: Sun, 27 Aug 2023 02:30:21 +0000 From: bugzilla-noreply@freebsd.org To: doc@FreeBSD.org Subject: [Bug 273374] Prepare to publish stable/14 expected end of life: August 31, 2028? Message-ID: <bug-273374-9-30ZA6oYbLn@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-273374-9@https.bugs.freebsd.org/bugzilla/> References: <bug-273374-9@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273374 Graham Perrin =E2=97=90 <grahamperrin@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Prepare to publish |Prepare to publish |stable/14 expected end of |stable/14 expected end of |life: 22 October 2028? |life: August 31, 2028? |(Based on the current | |schedule for 14.0-RELEASE) | --- Comment #3 from Graham Perrin =E2=97=90 <grahamperrin@gmail.com> --- Reading <https://www.freebsd.org/releases/13.0R/schedule/>:=20 * stable/13 branch created January 22, 2021 * releng/13.0 branch created February 5, 2021 * 13.0-RELEASE press release April 13, 2021 =E2=80=93 alongside <https://www.freebsd.org/security/#sup>; for stable/13:= =20 > =E2=80=A6 January 31, 2026 I imagine that 31st January was a (generously) rounded-up _end-of-month_ da= te that aims to keep a five-year promise from when stable/13 was branched. The proper date for an updated patch _might_ be end-of-month August 31, 202= 8. I'm freewheeling towards bikeshed territory =E2=80=93 with a question mark = in the summary line, which goes against proper use of Bugzilla (not for discussion= ) =E2=80=93 so I'll pause here, and not provide an update until after re@ can confirm or correct things.=20 Thanks --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-273374-9-30ZA6oYbLn>