Project

General

Profile

Bug #17376

Complete our release process doc wrt. non-final releases

Added by intrigeri 3 months ago. Updated 3 days ago.

Status:
In Progress
Priority:
Elevated
Assignee:
Category:
-
Target version:
Start date:
Due date:
% Done:

50%

Feature Branch:
doc/17376-finish-rc-post-release-steps
Type of work:
Contributors documentation
Blueprint:
Starter:
Affected tool:

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 wrongRejected

Bug #17565: Manual testing: SquashFS commentsConfirmed


Related issues

Related to Tails - Bug #17361: Streamline our release process Confirmed

Associated revisions

Revision 17d839e4 (diff)
Added by anonym 6 days ago

Release process: document post-release steps for RCs.

This is an initial attempt, which will tried for 4.5~rc1. I'm slightly
unsure if did the right thing with the two "thaw" instructions.

I opted to "fork" the steps for final releases, instead of adapting
them, to make things simpler. I'm sure we could make the same steps
work for both types of releases, but there would be a lot of "If you
just released a final release..." and so on, while an exhausted RM
likely would prefer more straightforward instructions.

Will-fix: #17376

History

#1 Updated by intrigeri 3 months ago

  • 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 3 months ago

  • Related to Bug #17361: Streamline our release process added

#3 Updated by anonym 3 months ago

  • 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 about 2 months ago

  • Target version changed from Tails_4.3 to Tails_4.4

#5 Updated by CyrilBrulebois 18 days ago

  • Target version changed from Tails_4.4 to Tails_4.5

#6 Updated by anonym 6 days ago

  • Status changed from Confirmed to In Progress

#7 Updated by anonym 6 days ago

  • 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.

Also available in: Atom PDF