Description of problem: All documents should have a document and release number. It is not necessary to follow the ISBN coding, but at least something similar. When I need or wish to report a correction, or an issue, my version of the document may not be the version that the maintainer is reviewing, and therefore, much energy is lost. Examples, Release Guide or installation guide or other If these guide were not separated on the web, into categories by links, we may be posting corrections to guides that are obsolete, or for other reason Version-Release number of selected component (if applicable): Not available, except by title. How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Document is missing a Document number and date of publication. Expected results: Technical, User, and other guides have a documentation number and a published date (or version). Additional info: If a document is updated, which is a reasonable action, the document number, version and date of release would allow one to know to obsolete his older version.
Hi, Every book already has a unique component name, which comes out as the same as a "document number" (e.g. "release-notes" is the unique identifier of the Fedora Release Notes, "install-guide" is the same for the Fedora Installation Guide). Every time we update a book we also create a new revision; you can see those in the Revision History, which is part of every book. For example, Fedora 22 Release Notes have revision history here: https://docs.fedoraproject.org/en-US/Fedora/22/html/Release_Notes/appe-Release_Notes-Revision_History.html From that page, you can see that the currently published version is 22-02. All other books we publish have a page like this.
Note that you can also right click on a page, select "View Page Info", and copy the package name. For example, Fedora-Release_Notes-22-en-US-1-0