Project

General

Profile

Bug #13483

Send a call for testing to build Tails 3.1 reproducibly to the rb-general mailing list

Added by u over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
-
Target version:
Start date:
07/18/2017
Due date:
% Done:

100%

Feature Branch:
451f:tails/feature/13483_blogpost
Type of work:
Communicate
Blueprint:
Starter:
Affected tool:

Description

anonym will draft the technical bits of this email and u will improve the draft and send it to the rb-general mailing list just after Tails 3.1 came out.

@anonym: please reassign to u when you've created the draft.

repro.mdwn (4.75 KB) anonym, 08/04/2017 01:03 PM


Related issues

Related to Tails - Feature #13624: Analyze results of Tails 3.1 call for reproduction Resolved 08/14/2017

History

#1 Updated by anonym over 2 years ago

  • File repro.mdwn added
  • Status changed from Confirmed to In Progress
  • Assignee changed from anonym to u
  • % Done changed from 0 to 30

u wrote:

@anonym: please reassign to u when you've created the draft.

Attached! I suggest [[!toc levels=3]] since it might make the "decision tree" easier to spot. :)

#2 Updated by u over 2 years ago

Thanks anonym.

I've prepared a blog post here: 451f:tails/feature/13483_blogpost.

Although I think in the beginning we were talking about an email only.
So what I will to is to send this email once 3.1 is out.

Beware: The text still needs a fix containing the SHA sum of Tails 3.1.

Then we can still decide if we want to publish this in our news too, some time later, or if we consider this to be too general public.

#3 Updated by u over 2 years ago

  • Feature Branch set to 451f:tails/feature/13483_blogpost

#4 Updated by u over 2 years ago

  • % Done changed from 30 to 60

#5 Updated by u over 2 years ago

  • Priority changed from Normal to High

#6 Updated by anonym over 2 years ago

  • Priority changed from High to Normal
  • % Done changed from 60 to 30

u wrote:

Although I think in the beginning we were talking about an email only.

Ah, that's right! Then we might want to convert at least the markdown links to footnotes for increased readability.

Beware: The text still needs a fix containing the SHA sum of Tails 3.1.

The RM (bertagaz, added as a watcher) is the authoritative source of this information.

Then we can still decide if we want to publish this in our news too, some time later, or if we consider this to be too general public.

Another consideration is that we likely will get a better signal-to-noise ratio if we only aim this at the Tails developer () and reproducible builds () communities. And maybe the Tor (tor-{dev,talk}@lists.torproject.org) community?

#7 Updated by bertagaz over 2 years ago

anonym wrote:

u wrote:

Beware: The text still needs a fix containing the SHA sum of Tails 3.1.

The RM (bertagaz, added as a watcher) is the authoritative source of this information.

Sent!

#8 Updated by u over 2 years ago

  • Priority changed from Normal to High
  • % Done changed from 30 to 60

Great idea anonym. Thanks bertagaz. I've prepared the email and I'm sort of waiting for 3.1 to be released.

#9 Updated by bertagaz over 2 years ago

u wrote:

Great idea anonym. Thanks bertagaz. I've prepared the email and I'm sort of waiting for 3.1 to be released.

It will take a bit more time than expected: in the end, I'm rebuilding the ISO to get the Linux upgrade. I'll send u the SHAAAAA.

#10 Updated by anonym over 2 years ago

  • Related to Feature #13624: Analyze results of Tails 3.1 call for reproduction added

#11 Updated by anonym over 2 years ago

  • Status changed from In Progress to Resolved
  • Assignee deleted (u)
  • % Done changed from 60 to 100

Also available in: Atom PDF