10076 2016-08-03 13:59:41 +0000 Docs should have pointer to latest manual at the top 2017-02-03 18:56:33 +0000 1 1 9 Documentation General Docs docs-general unspecified x86 Multiple RESOLVED FIXED 05 Feb 2017: RESOLVED Medium normal 2.3 M2 1 richard.purdie srifenbark sgw srifenbark --- --- Done (doc changes complete) oldest_to_newest 64832 0 richard.purdie 2016-08-03 13:59:41 +0000 https://imgur.com/a/S2cCd - people are finding old versions of the manual (and toaster mockups) when searching on google. We need to make it clearer where the latest versions of the manual are, even if this means tweaking headers on the older ones. The docs could have a link at the top saying "This is an old version of the manual; you may be interested in the latest here" for example. 64833 1 richard.purdie 2016-08-03 14:01:03 +0000 With python for example, there are clear selections/indications at the top of the page for 2.x verses 3.x manuals for example. 64838 2 srifenbark 2016-08-03 16:20:59 +0000 Richard, We have a note at the top of each manual currently but it points to that version. A variable is used to resolve the URL to the manual. The values come from a poky.ent file that uses the "YOCTO_DOCS_VERSION" in there to point to that release. If we put another link using "current" in there as the value for the most recent version of the manual for the most recent YP release, then the manual the user would get by clicking on the note link in a 1.8 manual would resolve to the 2.1 manual right now for example. I think I could alter that note so that it is clear that the manual they are looking at as a result of the title page is a specific version and then include a link to the "current" version of the manual. As long as it is acceptable to jump over major releases (e.g. from 1.7.3 to 2.1). Manual revision tables could be enhanced as well. There are some challenges with those. In general, the list of manuals is restricted to a particular branch. So the 1.8.x manuals do not list 2.0 or 2.1 manuals. Is that what we want? Or do we want to have all manuals listed regardless of major releases? Furthermore, an earlier version of a manual (e.g. 1.8) lists that version as the latest manual in the table when in fact 1.8.1 and 1.8.2 manuals exist. Scott 64839 3 srifenbark 2016-08-03 16:21:45 +0000 Setting up targets, etc. 67560 4 srifenbark 2016-10-25 20:13:10 +0000 Moving to 2.3 M2 68133 5 srifenbark 2016-11-08 17:56:13 +0000 Any further thoughts on this Richard? 69569 6 richard.purdie 2017-01-06 12:50:50 +0000 Sorry Scott, this got lost in other emails. Currently at the top of the manual you have "For the latest version of this manual associated with this Yocto Project release, see the Yocto Project Mega-Manual from the Yocto Project website.". I think I'd like to see each of the manual have something like this at the top: "For the latest version of this manual associated with this Yocto Project release, see the Yocto Project Mega-Manual from the Yocto Project website here. There may be later releases of the project and the latest release can be found on https://www.yoctoproject.org/documentation. The manual for the latest in-development version of the project are available at http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html" So put in links to how to find the latest release (the main docs page) and how to find the latest in progress version. Does that make sense? 69685 7 srifenbark 2017-01-10 21:48:32 +0000 Richard, See http://www.yoctoproject.org/docs/2.3/yocto-project-qs/yocto-project-qs.html#yocto-project-qs-intro for the QS version of the new note. I would like to agree on the new note before updating the rest of the manuals. Thanks, Scott 70287 8 srifenbark 2017-01-31 16:29:48 +0000 I need Richard to address Comment 7. Setting to 2.3 M3. 70396 9 srifenbark 2017-02-02 18:32:30 +0000 Richard, See http://www.yoctoproject.org/docs/2.3/yocto-project-qs/yocto-project-qs.html#yocto-project-qs-intro for your latest suggestions. Thanks, Scott 70425 10 srifenbark 2017-02-03 18:56:33 +0000 Hi, After consulting with Richard, we determined the best solution for the note at the beginnings of the manuals to more clearly show the current, alternate, and latest versions of the manual depending on the release. Each manual has been updated and the wording approved by Richard Purdie. Marking the bug as RESOLVED and setting the doc flag to "done." Scott