Document the removal of read-only persistence
The following documentation refer to read-only persistence, that we removed in 3.0:
#4 Updated by sajolida over 2 years ago
We very rarely document changes themselves in the doc. We do it when some migration is required by the user or before removing big features but I don't think this applies here. Most of the time we only update the documentation to be in sync with what's actually implemented in the current Tails.
I would say that this ticket is only about updating the documentation to stop mentioning the read-only persistence in time for 3.0.
We do this by doing a Git branch from feature/stretch (the base branch for 3.0) and updating the doc there. It will then be applied automatically to the website when 3.0 get released.
Very happy if you take it over!
#6 Updated by sajolida over 2 years ago
- Status changed from Confirmed to In Progress
- Assignee changed from sajolida to intrigeri
- QA Check changed from Ready for QA to Info Needed
- Starter deleted (
Thanks for taking that work from my plate! Your branch was perfect so I merged it into feature/stretch.
And you correctly branched it from feature/stretch, that's so cool you figured that out by yourself.
Regarding the naming of branches, we use loose a convention of naming documentation branches doc/XXXXX-some-short-description, where XXXXX is the ticket number. When dealing with many branches I find the short description useful to recognize which branch I'm dealing with (as I don't have all the ticket numbers in mind, thankfully!). But if you prefer it differently, I'll deal with it.
I'm reassigning to intrigeri and removing the Easy flag because I see mentions of this feature the design documentation.
intrigeri: Will you take care of it? Shall I reassign to Alan? Try to do it myself?