[Bug 264326] releng/ (Release Engineering Information): update, since 13.1-RELEASE was announced around two weeks ago
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 264326] releng/ (Release Engineering Information): update, since 13.1-RELEASE was announced around two weeks ago"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 264326] www: releng/ describes FreeBSD 13.1 as upcoming"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 264326] www: releng/ describes FreeBSD 13.1 as upcoming"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 264326] www: releng/ describes FreeBSD 13.1 as upcoming"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 29 May 2022 08:33:19 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264326
Bug ID: 264326
Summary: releng/ (Release Engineering Information): update,
since 13.1-RELEASE was announced around two weeks ago
Product: Documentation
Version: Latest
Hardware: Any
URL: https://github.com/freebsd/freebsd-doc/tree/main/websi
te/content/en/releng
OS: Any
Status: New
Severity: Affects Many People
Priority: ---
Component: Website
Assignee: doc@FreeBSD.org
Reporter: grahamperrin@gmail.com
<https://www.freebsd.org/releng/> describes FreeBSD 13.1 as upcoming.
Re:
<https://github.com/freebsd/freebsd-doc/commit/6968857e4a282927e0d4245c4821f04402f29827>
I assume that after a RELEASE, if no other RELEASE is scheduled, it's customary
to:
* comment out the relevant section
* make visible a line to signify that nothing is scheduled.
For now, maybe:
> As of 2022-05-17, there is not a schedule for the next release.
– or more simply:
> Nothing scheduled.
For what it's worth, I prefer terse here. (From texts elsewhere, it should be
clear that there's not always something scheduled.)
--
You are receiving this mail because:
You are the assignee for the bug.