I've tried to document what I understand our current consensus to be: it's generally still preferred to build server packages for releases that only touch code running on Tails workstations, but in some cases, we may issue Tails-only releases due to time sensitivity and team availability considerations. Given that we may issue such releases again in future, I've also tried to document specific considerations that apply so we don't have to answer the same questions again (Do we publish a release object? Do we do all the regular release comms? etc.).
Status
Ready for review
Description of Changes
I've tried to document what I understand our current consensus to be: it's generally still preferred to build server packages for releases that only touch code running on Tails workstations, but in some cases, we may issue Tails-only releases due to time sensitivity and team availability considerations. Given that we may issue such releases again in future, I've also tried to document specific considerations that apply so we don't have to answer the same questions again (Do we publish a release object? Do we do all the regular release comms? etc.).
Checklist (Optional)
make docs-lint) passed locallymake docs-linkcheck) passedmake docs) docs at http://localhost:8000