Project

General

Profile

Bug #15997

Feature #15292: Distribute a USB image

Test and release new Tails Verification

Added by Anonymous over 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
09/28/2018
Due date:
% Done:

0%

Estimated time:
4.00 h
Feature Branch:
verification-extension:usbimage
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Description

Reviewer and rubber-duck: intrigeri


Related issues

Blocked by Tails - Bug #15995: Have Tails Verification handle IDFs with several Tails installation paths (ISO/IMG) Resolved 09/28/2018
Blocked by Tails - Bug #16171: Get our master branch ready for IDF v2 and new Tails Verification extension Resolved 11/29/2018

History

#1 Updated by Anonymous over 1 year ago

  • Blocked by Bug #15995: Have Tails Verification handle IDFs with several Tails installation paths (ISO/IMG) added

#2 Updated by intrigeri over 1 year ago

  • Description updated (diff)

#3 Updated by intrigeri about 1 year ago

Not sure where I should write this because it's about coordinating stuff that's happening in a bunch of different tickets assigned to different people.

Given the IDF format will change, we'll switch to install/v2/**/*.json. So we'll need to talk a bit about how we coordinate three things:

  • when we start publishing install/v2/**/*.json (#15999)
  • when we stop publishing install/v1/**/*.yml (#15999 too)
  • when you release the new Tails Verification (this very ticket)
  • when the install doc starts requiring the new version of Tails Verification

The only part of that on which I'll need an answer soon is "when we stop publishing install/v1/**/*.yml": depending on our plan, either I'll replace v1 generation with v2, or I'll keep generating v1 for some time if that's useful.

So let's talk, e.g. during or after the next USB image meeting :)

#4 Updated by sajolida about 1 year ago

We can force people to update their version of the extension and this work pretty well.

If you're curious, see https://addons.mozilla.org/en-US/firefox/addon/tails-verification/statistics/usage/versions/?last=30.

Login: keyringer internal decrypt credentials.asc | grep addons.mozilla.org

So we don't need to ship both v1 and v2 in parallel during several days, only during the transition to make sure that nobody gets a broken download page. I think it's enough for me to have all the pieces ready and deal with the change from v1 to v2 during the release of the new extension. I mean in the same day:

  1. Test the new extension locally.
  2. Add v2 on the website.
  3. Release the new extension.
  4. Test the new extension remotely.
  5. Force the new extension on the website.
  6. Remove v1 from the website.

For me to do this alone, I guess I would only need a branch that adds v2. I can remove v1 with a git rm.

We could even leave v1 around until the next release. It shouldn't be necessary but I don't see how it could hurt.

#5 Updated by intrigeri about 1 year ago

  • Blocked by Bug #16171: Get our master branch ready for IDF v2 and new Tails Verification extension added

#6 Updated by intrigeri about 1 year ago

sajolida wrote:

We can force people to update their version of the extension and this work pretty well.

Excellent!

Your plan totally makes sense to me.

For me to do this alone, I guess I would only need a branch that adds v2.

I've prepared it on #16171.

I can remove v1 with a git rm.
We could even leave v1 around until the next release. It shouldn't be necessary but I don't see how it could hurt.

Indeed, I see no reason to both removing it particularly early: my branch for #15999 deletes it and removes the doc that leads the RM to generate it. That branch will be merged into devel at the same time as the rest of our USB image work, targetted at 3.12.

#7 Updated by sajolida about 1 year ago

  • Target version changed from Tails_3.11 to Tails_3.12

#8 Updated by Anonymous about 1 year ago

  • Parent task changed from #15994 to #15292

#9 Updated by Anonymous about 1 year ago

  • Feature Branch set to verification-extension:usbimage

This is now ready to be published.

It's not been merged to master, I trust you to do that once happy.
I think you'll need to adjust the minimum version in the download pages.

#10 Updated by sajolida about 1 year ago

#11 Updated by sajolida about 1 year ago

#12 Updated by sajolida about 1 year ago

  • Assignee changed from sajolida to Anonymous
  • QA Check set to Info Needed

Hey,

My local tests for ISO images went super smoothly, congrats!

I didn't know how to test USB images as the IDF on the production website only mentions the ISO file.

How can I test that 2.0 works fine with USB images?

Still, as we're only shipping ISO images as of now, I released version 2.0 on the app stores anyway.

But I really want to test 2.0 with USB images before we release 3.12.

#13 Updated by sajolida about 1 year ago

  • Status changed from Confirmed to Resolved
  • Assignee deleted (Anonymous)
  • QA Check deleted (Info Needed)

I found out how to make the extension use a different IDF that I uploaded on another server and tested the verification of a USB image in different ways. Everything worked as expected. Excellent!

So I think we can close this ticket :)

#14 Updated by Anonymous about 1 year ago

Great!

If you can, it would be interesting to report the spent time on this task, so we can later compare that to the estimation. I would like to make that a habit for future projects :)

Also available in: Atom PDF