doc/releases: access main releases page from top-level TOC #30598
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
smithfarm
requested review from
LenzGr,
batrick,
theanalyst,
cbodley,
sebastian-philipp,
dillaman and
liewegas
|
jenkins render docs |
smithfarm
force-pushed
the
wip-doc-releases-toc
branch
2 times, most recently
from
f0250ff
to
a959c64
Compare
|
jenkins render docs |
|
Doc render available at http://docs.ceph.com/ceph-prs/30598/ |
smithfarm
force-pushed
the
wip-doc-releases-toc
branch
from
a959c64
to
34c394f
Compare
Before this commit, one had to go through the releases index to get to the main releases page. This should be the other way around. Also, the main releases page should not be called "schedule.rst" - while it contains a release timeline, that's not its principal purpose. Rename the page to "general.rst" and move the "Understanding the release cycle" section before the timeline. Signed-off-by: Nathan Cutler <ncutler@suse.com>
smithfarm
force-pushed
the
wip-doc-releases-toc
branch
from
34c394f
to
e12ac2d
Compare
|
jenkins render docs |
|
I wonder if (almost) the very bottom of the TOC is the right place for "Releases". I'm also leaning towards having just one "Releases" TOC item pointing to the main release page, and linking to the release index from there (i.e., the exact opposite of what we have now). |
|
Doc render available at http://docs.ceph.com/ceph-prs/30598/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before this commit, one had to go through the releases index to get to the main releases page. This should be the other way around.
Also, the main releases page should not be called "schedule.rst" - though it contains a historical timeline, that is not its principal purpose. Rename the page to "general.rst" and move the "Understanding the release cycle" section before the timeline.