Project

General

Profile

Bug #17376

Complete our release process doc wrt. non-final releases

Added by intrigeri about 2 months ago. Updated 11 days ago.

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

0%

Feature Branch:
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.


Related issues

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

History

#1 Updated by intrigeri about 2 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 about 2 months ago

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

#3 Updated by anonym about 2 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 11 days ago

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

Also available in: Atom PDF