Bug #11126

Publish Torrents for beta and RCs

Added by sajolida 2016-02-14 11:23:57 . Updated 2016-02-25 18:15:58 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_2.2
Start date:
2016-02-14
Due date:
% Done:

100%

Feature Branch:
Type of work:
Contributors documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

As decided in Feature #10915. Now we need to adjust the release process:

Our release process doc already makes us generate a Torrent and its
detached signature, even for RC:s in the “Generate the OpenPGP signatures and Torrents” which seems to have no condition attached. It also makes us seed this Torrent unconditionally.

But we need to change:

  • in the “Update the website and Git repository” section: don’t skip
    the Torrent publication steps when preparing a RC; also deal with
    cleaning RC:s’ Torrent files later

Subtasks

History

#1 Updated by sajolida 2016-02-14 11:36:24

#2 Updated by sajolida 2016-02-14 12:54:52

  • Status changed from New to Confirmed
  • Assignee changed from sajolida to anonym

In the end, this might be slightly bit more complex than I thought at first sight :)

Reassigning to anonym who’s the one who knows this document the best (and who suggested Feature #10915). bertagaz could do it too probably.

#3 Updated by anonym 2016-02-25 18:15:58

  • Status changed from Confirmed to Resolved
  • Assignee deleted (anonym)
  • % Done changed from 0 to 100
  • QA Check set to Pass