Feature #12206

Ensure 3.0~beta1 can be incrementally upgraded to 3.0~beta2, etc.

Added by intrigeri 2017-02-01 13:17:06 . Updated 2017-02-01 15:43:23 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Target version:
Tails_3.0
Start date:
2017-02-01
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Upgrader
Deliverable for:

Description

I think the nicest way to do that is to configure /etc/os-release so that the alpha update channel is used. And we’ll revert that in 3.0 final.

To avoid breaking the test suite, an UDF for 1.0~test / amd64 should be added to the alpha channel.

Subtasks

Related issues

Blocks Tails - Feature #12195: Ask contributors to upgrade to 3.0~betaN Resolved 2017-01-30
Blocks Tails - Feature #12207: Announce Tails 3.0~beta1 Resolved 2017-02-01

History

#1 Updated by intrigeri 2017-02-01 13:17:46

  • blocks Feature #12195: Ask contributors to upgrade to 3.0~betaN added

#2 Updated by intrigeri 2017-02-01 13:26:03

  • Description updated

#3 Updated by intrigeri 2017-02-01 13:45:43

  • Assignee changed from intrigeri to anonym

(for the test suite bits)

#4 Updated by intrigeri 2017-02-01 15:40:14

#5 Updated by anonym 2017-02-01 15:43:24

  • Status changed from Confirmed to Resolved
  • Assignee deleted (anonym)