Old EOL-ed release landing pages have master (up-to-date) document links
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Security Guide Documentation |
Fix Released
|
Undecided
|
Farhan Kalsekar | ||
openstack-manuals |
Fix Released
|
Low
|
Farhan Kalsekar |
Bug Description
There are landing pages for EOL-ed releases such as kilo and liberty:
https:/
https:/
The problem is that the pages also have links for Administrator Guide, High Availability Guide,
Operations Guide, Security Guide, Virtual Machine Image Guide, Architecture Design Guide,
API Guide (api-quick-start), End User Guide, and so on for "master" branches.
Master branch documentation usually contains the content with up-to-date releases, not previous releases.
New users might be so confused.
I think the candidate solutions are:
- Remove all links for master branch documents
- Adds an explanation: the master branch documents may not have kilo/liberty explanations.
Changed in openstack-manuals: | |
status: | New → Confirmed |
importance: | Undecided → Low |
milestone: | none → pike |
Changed in openstack-manuals: | |
assignee: | nobody → Farhan Kalsekar (ifarhan) |
Changed in ossp-security-documentation: | |
assignee: | nobody → Farhan Kalsekar (ifarhan) |
Changed in openstack-manuals: | |
assignee: | Farhan Kalsekar (ifarhan) → Alexandra Settle (alexandra-settle) |
Changed in openstack-manuals: | |
assignee: | Alexandra Settle (alexandra-settle) → Farhan Kalsekar (ifarhan) |
Changed in ossp-security-documentation: | |
status: | In Progress → Fix Released |
Changed in openstack-manuals: | |
status: | In Progress → Fix Released |
Some of the docs like the Admin guide, HA guide, Security guide etc does explicitly state at the start
"This guide documents OpenStack Ocata, Newton, and Mitaka releases."
Would adding this line to the other docs as applicable be an acceptable solution?