Project

General

Profile

Feature #16143

Clean up mirror-dispatcher.js

Added by u 11 months ago. Updated about 2 months ago.

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Installation
Target version:
-
Start date:
11/19/2018
Due date:
% Done:

0%

Feature Branch:
mirror-pool-dispatcher.git:feature/15750+cleanup
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Description

While looking into #15750, I saw there was some old code which is now obsolete. It was used by DAVE, but since we switched to VE, it's not necessary.

This is not urgent and can be reviewsd at any time - maybe when we release the next version of the verification extension, so it can be tested at the same time.


Related issues

Related to Tails - Feature #15750: Help people who download from a broken mirror Confirmed 07/29/2018
Related to Tails - Bug #15995: Have Tails Verification handle IDFs with several Tails installation paths (ISO/IMG) Resolved 09/28/2018

History

#1 Updated by u 11 months ago

  • Related to Feature #15750: Help people who download from a broken mirror added

#2 Updated by u 11 months ago

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

#3 Updated by u 11 months ago

  • Assignee changed from sajolida to u
  • QA Check changed from Ready for QA to Dev Needed

But now I see I missed a detail, and intrigeri needs to look into it, because it will affect the Upgrader. Taking it back for now.

#4 Updated by intrigeri 11 months ago

But now I see I missed a detail, and intrigeri needs to look into it, because it will affect the Upgrader. Taking it back for now.

Sure, please reassign to me whenever it's time to do my bit :)

#5 Updated by u 7 months ago

  • Target version changed from Tails_3.13 to Tails_3.15

I would like to ask Enrico to do this, if we work again on the Verification Extension (in order to obsolete it).
In any case, it won't happen anytime soon.

#6 Updated by CyrilBrulebois 3 months ago

  • Target version changed from Tails_3.15 to Tails_3.16

#7 Updated by intrigeri about 2 months ago

  • Target version deleted (Tails_3.16)

Hi!

We've set up an automated process to ask our fellow contributors to update some tickets of theirs, in order to:

  • better reflect your plans;
  • bring down your amount of work-in-progress to a sustainable level;
  • encourage team work and increase the chances that someone finishes the work;
  • avoid a human doing ticket triaging and asking you the same questions on each such ticket.

In particular, this process identifies:

  • Stalled work-in-progress
  • Reviews waiting for a long time

However, in the current state of things, this process is not able to notice those tickets when their Target version has been repeatedly postponed by our Release Managers. Therefore, the ticket triaging team decided on #16545 to remove the Target version whenever in such cases, when it does not feel realistic. This is what I'm doing on this ticket.

You now have a few options, such as:

  • Deassign yourself. That's fine. If it really matters, someone else, possibly you, may pick it up later. Then, if this ticket is relevant for a Tails team, bring it to their attention; else, forget it and take care of yourself :)
  • If you think you can realistically come back to it and finish the work in the next 6 months, say so on this ticket, for example by setting a suitable "Target version". This will communicate your plans to the rest of the project and ensure the task pops up on your radar at a suitable time. Of course, you can still realize later that it is not going to work as planned, and revisit today's choice.

Cheers!

Also available in: Atom PDF