Feature #11234

Explain how to use check-mirrors in the release process

Added by sajolida 2016-03-14 14:40:14 . Updated 2016-04-26 09:13:13 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2016-03-14
Due date:
% Done:

100%

Feature Branch:
doc/11234-explain-check-mirrors
Type of work:
Contributors documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

The release process document in /contribute/release_process#index27h2 is
not clear about how to verify that mirrors are synced with the latest
upload.

We should write check-mirrors snippets to make this easier.


Subtasks


History

#1 Updated by sajolida 2016-04-14 09:01:43

  • Assignee changed from sajolida to anonym
  • Target version set to Tails_2.3
  • QA Check set to Ready for QA
  • Feature Branch set to doc/11234-explain-check-mirrors

Using your snippet.

#2 Updated by sajolida 2016-04-14 09:02:13

  • Status changed from Confirmed to In Progress

Applied in changeset commit:324a38cb2de35282d6c4528036b8884a2a602a07.

#3 Updated by anonym 2016-04-22 06:53:03

  • Status changed from In Progress to Fix committed
  • Assignee deleted (anonym)
  • % Done changed from 0 to 100
  • QA Check changed from Ready for QA to Pass

Looks great! FWIW, that’s what I did for the last release.

#4 Updated by anonym 2016-04-26 09:13:13

  • Status changed from Fix committed to Resolved