Red Hat Bugzilla – Bug 155179
Standard notice for legacy and obsoleted documents ?
Last modified: 2009-07-07 00:08:54 EDT
Description of problem:
Following discussion on fedora-docs-list re: Legacy, it may (or may not) be
useful to have standard notices for documents at different stages of support
(Current/Legacy/Obsolete), in the same way that there is a standard notice for
Mailing list link:
Attached is a possible "Obsolete Document" notice, similar to the draft notice.
Version-Release number of selected component (if applicable): N/A
Read an old document :)
It may not be obvious whether the document is current or not.
Is obvious that the document is historical, and there is a link to the Website
to look for a later version.
Created attachment 113293 [details]
Possible "Obsolete Document" notice
Created attachment 113294 [details]
Possible "Legacy Document" notice
Stuart, I like the text you wrote. I made only minor style revisions. Should
we tie this in with a required &FCLOCALVER; entity, so that when a reader gets a
legacy or obsolete document, they know exactly at which version of Fedora Core
their document version stalled?
I would say yes...perhaps file a separate RFE and cross-link them ?
&FCLOCALVER; may be a separate issue from stamping documents as
Safe/Old/At-Your-Own-Risk, as the new entity could be used within the text, as
well as the header.
When we agree the process we could make a mock document and run it all the way
through the lifecycle, with both the headers and entity to see how they work out
These guides are no longer being supported or updated. If you feel your ticket could better be supported in one of our other guides please feel free to reopen and reassign the ticket to that guide.
Thank you for taking the time to submit your bug.
Ticket moved to allow products to be removed from BZ.