Feature #12628

Draft a "user" (aka. RM) story for the reproducible release process

Added by Anonymous 2017-06-02 12:42:20 . Updated 2017-06-22 13:51:23 .

Status:
Duplicate
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2017-06-02
Due date:
% Done:

0%

Feature Branch:
Type of work:
Contributors documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:
289

Description

Let’s draft a user story for the RM. Here are some notes:

once I have built my own release .iso, instead of uploading it I just generate the .sig and send it to Jenkins somehow. if it managed to build an .iso that that .sig can verify, then it will publish the ISO itself
this ensures that we never release something that hasn’t been reproduced once, and makes bandwidth less important for RMs

Subtasks

Related issues

Is duplicate of Tails - Bug #12629: Document reproducible release process Resolved 2017-06-02

History

#1 Updated by Anonymous 2017-06-02 12:44:11

  • related to Bug #12629: Document reproducible release process added

#2 Updated by intrigeri 2017-06-02 12:49:49

  • Status changed from New to Confirmed
  • Assignee changed from intrigeri to anonym
  • Deliverable for set to 289

#3 Updated by intrigeri 2017-06-22 13:51:00

  • related to deleted (Bug #12629: Document reproducible release process)

#4 Updated by intrigeri 2017-06-22 13:51:11

  • is duplicate of Bug #12629: Document reproducible release process added

#5 Updated by intrigeri 2017-06-22 13:51:23

  • Status changed from Confirmed to Duplicate
  • Assignee deleted (anonym)
  • Target version deleted (SponsorT_2016)