Not that I have much weight, because of lack of participation, but I think this is a great idea. Finding obsolete documentation as users can be frustrating. I agreed with all parts of the "Proposed path forward" in Issue 183.

At one time I had started reading the documentation looking for ways to eliminate and replace with all specific reference to release #'s with general references so that when a user gets to the documentation site it always reads as if this works for the current version of Fedora. Then I wondered what would happen if in the next release something did change making that piece of documentation only applicable to the previous release, how would you find those easily and to make the documentation catch up with the current release.

Thanks Matthew for finding an additional way to put more polish on a great distribution.

----------------------------------------------
| Steve | mowestusa@yahoo.com |
----------------------------------------------


On Friday, November 26, 2021, 03:41:02 PM EST, Matthew Miller <mattdm@fedoraproject.org> wrote:


On Fri, Nov 26, 2021 at 02:32:03PM -0500, Matthew Miller wrote:
> Let's make that decision now, then. Heading to
> https://pagure.io/fedora-docs/docs-fp-o/issue/118 to not split the
> discussion.

Proposed path forward: https://pagure.io/fedora-docs/docs-fp-o/issue/183



--
Matthew Miller
<mattdm@fedoraproject.org>
Fedora Project Leader
_______________________________________________
docs mailing list -- docs@lists.fedoraproject.org
To unsubscribe send an email to docs-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure