Project

General

Profile

Bug #17413

Document process for emergency releases

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

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

0%

Feature Branch:
Type of work:
Contributors documentation
Blueprint:
Starter:
Affected tool:

Description

Not all steps on wiki/src/contribute/working_together/roles/release_manager.mdwn make sense for an emergency release. During emergency response situations, having good doc / checklists to follow without too much guess work is really useful.

kibi suggests we have "a little page, or paragraph, summing up things for emergency releases", with basically this:

  1. agreeing we need one
  2. deciding about the timing
  3. announce the code freeze
  4. talking to people (tails@, testers, tech writers, TR)
  5. creating a target version on Redmine

Related issues

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

History

#1 Updated by intrigeri 3 months ago

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

#2 Updated by intrigeri 3 months ago

  • Description updated (diff)

Also available in: Atom PDF