Clean some outdated instructions and proposal about version-related directives #1584
Conversation
Only for R4.3, do not merge in 4.2 branch
| Subdividing the page into clearly-labeled sections for each release has several benefits: |
There was a problem hiding this comment.
What is the reason for dropping the rationale behind the use of release specific metadata?
There was a problem hiding this comment.
From my understanding, QubesOS/qubes-issues#5308 is resolved. So I thought that we won't keep what I believe are outdated instructions:
We now use a different branch for each release, so the following paragraphs are outdated, right?
We maintain only one set of documentation [...]
Subdividing the page into clearly-labeled sections for each release has several benefits:
... and the following list items.
By contrast, an alternative approach, such as segregating the documentation into two different branches, would mean [...]
There is something wrong with this part of the guide but maybe I'm wrong about what to do with it?
I believe the removed part is now outdated, considering that QubesOS/qubes-issues#5308 is closed. Also, I would like to make a proposal to mention change between versions.
parulin
force-pushed
the
custom-persist-version-added
branch
from
1672b84 to
1449df1
Compare
2 participants
This was meant to be a minor commit, adding some
versionaddeddirective. I then realized that the reStructuredText documentation style guide was outdated so I made a proposal to make a consistent use of the Sphinx directives related to changes between versions.This PR is meant to be part of the R4.3 documentation, not the R4.2 one.