Simple bugs with image impact for the project...

From: Mason Loring Bliss <mason_at_blisses.org>
Date: Sat, 10 Sep 2022 21:12:14 UTC
I'd noted FreeBSD 13.0's end of life on IRC a couple times, and then opened
a bug to have it removed from the freebsd.org front page. Between my live
mentions and opening a bug, Graham Perrin opened his own, and found more
things to correct, so his is the right one to drive forward. But here we
are, September 10th, heading towards two weeks of 13.0 no longer having
formal support, and the main page still notes 13.0 as being supported.

This feels like something that ought to be so trivially easy to correct as
to not warrant mention, but instead it seems to be dragging on, and it
seems like a problem that the project can't post correct and up to date
information about itself on the web site, despite at least a couple people
interested in seeing it updated, one of whom (Graham) has a commit bit, as
I understand it.

What's missing?

Please take this as a desire to understand the current state and to see
process improvement, not as a complaint about volunteers not doing work on
a schedule. (That said, I'd volunteer if that'd make it happen. I updated
the Torrents wiki page, moving 13.0 out of current releases, because I
could, but I (appropriately, since I'm not formally tied to the project)
don't have access to update the main web site.)

-- 
Mason Loring Bliss  ((   If I have not seen as far as others, it is because
 mason@blisses.org   ))   giants were standing on my shoulders. - Hal Abelson