Feature #12628

Feature #5630: Reproducible builds

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

Added by u about 2 months ago. Updated about 1 month ago.

Status:DuplicateStart date:06/02/2017
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
QA Check: Blueprint:
Feature Branch: Easy:
Type of work:Contributors documentation Affected tool:

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


Related issues

Duplicates Tails - Bug #12629: Document reproducible release process In Progress 06/02/2017

History

#1 Updated by u about 2 months ago

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

#2 Updated by intrigeri about 2 months ago

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

#3 Updated by intrigeri about 1 month ago

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

#4 Updated by intrigeri about 1 month ago

  • Duplicates Bug #12629: Document reproducible release process added

#5 Updated by intrigeri about 1 month ago

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

Also available in: Atom PDF