Bug #17376
Complete our release process doc wrt. non-final releases
50%
Description
There are various areas where there aren’t very specific instructions when it comes to non-final releases. For example:
> XXX: adapt / fork for release candidates. In the meantime, read all this, and skip what does not make sense for a RC.
This is kinda scary for someone who has never RM’ed a non-final release (alpha, beta, RC). We should fix that.
Ideally, someone who’s already RM’ed a non-final release would test the resulting updated instructions while RM’ing a real non-final release, before a RM who never did that goes through it.
Subtasks
| Bug #17557: “Update other base branches” feels wrong | Rejected | 0 |
|||
| Bug #17565: Manual testing: SquashFS comments | Confirmed | 0 |
History
#1 Updated by intrigeri 2019-12-25 13:27:17
- Assignee set to anonym
Rationale: kibi can’t do this and IMO this fits better into the “secondary RM” role (anonym) than in the “backup RM” one (intrigeri).
#2 Updated by intrigeri 2019-12-26 17:45:11
- related to Bug #17361: Streamline our release process added
#3 Updated by anonym 2019-12-27 14:41:45
- Target version set to Tails_4.3
Must be ready before the next major release, when kibi is gonna prepare the RC.
#4 Updated by anonym 2020-02-11 15:26:39
- Target version changed from Tails_4.3 to Tails_4.4
#5 Updated by CyrilBrulebois 2020-03-12 09:56:03
- Target version changed from Tails_4.4 to Tails_4.5
#6 Updated by anonym 2020-03-24 14:21:54
- Status changed from Confirmed to In Progress
Applied in changeset commit:tails|17d839e44383af1e43f4c969f61c59f565cc0b68.
#7 Updated by anonym 2020-03-24 14:27:56
- Feature Branch set to doc/17376-finish-rc-post-release-steps
The feature branch has instructions that I am reasonably confident in. @kibi, let’s try them tomorrow! I’ll make extra sure to be around when you perform them. Also, there’s Thursday. :)
I’ll keep the branch assigned to me until after we have followed them, and done any potential follow-ups.
#8 Updated by CyrilBrulebois 2020-04-07 17:05:21
- Target version changed from Tails_4.5 to Tails_4.6
#9 Updated by anonym 2020-04-14 13:47:30
- Status changed from In Progress to Needs Validation
- Assignee changed from anonym to CyrilBrulebois
Cyril, so now with 4.5 completely released, do you think anything is still missing/wrong?
Otherwise I guess we can ask intrigeri to look at commit:17d839e44383af1e43f4c969f61c59f565cc0b68 and see if he has some comments or if we can close this ticket already.
#10 Updated by CyrilBrulebois 2020-04-14 13:52:15
I’ve got a lot of feedback, but I had delayed this until the tentative switch to GitLab.
It might make sense to close this ticket now though, and I’ll follow up with (I think) a branch with easy commits plus a ticket with another part that could contain less trivial changes.
#11 Updated by CyrilBrulebois 2020-04-28 07:24:58
- Status changed from Needs Validation to Resolved
I’ve worked on two branches with proposed changes regarding release candidates and final major releases, which I’ve filed as Bug #17659; closing this ticket accordingly.