Feature #12615: Consider basing Tails on quarterly snapshots of Debian testing

Feature #12615

Consider basing Tails on quarterly snapshots of Debian testing

Added by intrigeri 2017-05-30 08:40:01 . Updated 2019-03-08 15:31:33 .

Status:

In Progress

Priority:

Normal

Assignee:

Category:

Target version:

Tails_5.0

Start date:

2017-06-13

Due date:

% Done:

74%

Feature Branch:

Type of work:

Research

Blueprint:

https://tails.boum.org/blueprint/Debian_testing/

Starter:

Affected tool:

Deliverable for:

Description

According to our plan (https://tails.boum.org/blueprint/Debian_Stretch/#rolling), we should decide whether we start tracking Debian testing soonish, so that if we choose to do so, we can start tracking Debian testing ~6 months after the Debian Stretch release, i.e. around December, 2017. The major release on our schedule that’s closest to this date is 3.4, that we plan to release on 2018-01-16. So we should analyze how the Stretch porting went etc., as the blueprint describes, early enough to make it feasible to release something based on Debian testing in January 2018. I think we should:

do the research/analysis before Tails summit
- I’m not available in August so I’ll try to do my share by the end of July
- others (mostly anonym for the test suite part, our doc writers, and perhaps our Debian person) can get started whenever they want; let me know if having subtasks assigned to one of you for each area that needs some work would help you keep track of it :)
make a decision during Tails summit

Then, if we decide to walk the rolling path, we’ll have 4.5 months to handle the transition, which should be enough I guess.

Files

gitstats-2.x-to-3.0.tar.bz2 (207134 B)

intrigeri, 2017-06-13 09:03:23

Subtasks

Feature #12690: Gather & analyze data about the Stretch cycle: test suite

Rejected

anonym

Feature #12691: Gather & analyze data about the Stretch cycle: documentation

Resolved

100

Feature #14514: Porting Tails to Buster: organize first code + test suite sprint

Resolved

anonym

100

Feature #14577: Porting Tails to Buster: organize second code + test suite sprint

Resolved

100

Feature #14578: Decide when we want to release Tails based on Debian Bullseye

Confirmed

Feature #14579: Tell the Technical Writers what part of our doc needs to be updated for Buster

Confirmed

Feature #14791: Design how the Foundations Team will tell the Technical Writers what part of our doc needs to be updated

Resolved

100

Feature #14814: Analyze test suite results on Buster: 2017-10 sprint

Rejected

anonym

Feature #14823: Simulate tracking of security updates on a branch based on snapshots of Debian testing

Confirmed

Related issues

Related to Tails - ~~Bug #14622~~: Have the Installer detect when "Clone the current Tails" won't fit in the destination partition before deleting anything	Resolved	2017-09-11
Related to Tails - Feature #11881: Disable preview in Nautilus by default to prevent potential execution of malicious data	Confirmed	2016-10-20

History

#1 Updated by intrigeri 2017-06-13 08:25:22

Description updated

#2 Updated by intrigeri 2017-06-13 08:55:34

File <del>missing: gitstats-2.x-to-3.0.tar.bz2</del> added

To start with, here are some stats about our Jessie..Stretch (i.e. currently stable..testing) activity in Git.

#3 Updated by intrigeri 2017-06-13 09:03:08

File deleted (~~gitstats-2.x-to-3.0.tar.bz2~~)

#4 Updated by intrigeri 2017-06-13 09:03:26

File gitstats-2.x-to-3.0.tar.bz2 added

#5 Updated by intrigeri 2017-06-13 13:59:54

Status changed from Confirmed to In Progress
Target version changed from Tails_3.1 to Tails_3.2

intrigeri wrote:
> # do the research/analysis before Tails summit
> I’m not available in August so I’ll try to do my share by the end of July

Done: https://tails.boum.org/blueprint/Debian_Stretch/#rolling-stretch-analysis

> others (mostly anonym for the test suite part, our doc writers, and perhaps our Debian person) can get started whenever they want;

I’ve created two subtasks and assigned them to the relevant people.

#6 Updated by intrigeri 2017-06-13 14:00:38

Feature Branch set to https://tails.boum.org/blueprint/Debian_Stretch/#rolling

#7 Updated by intrigeri 2017-06-13 14:00:53

Feature Branch deleted (~~https://tails.boum.org/blueprint/Debian_Stretch/#rolling~~)
Blueprint set to https://tails.boum.org/blueprint/Debian_Stretch/#rolling

#8 Updated by intrigeri 2017-06-29 10:23:01

blocks ~~Feature #13234~~: Core work 2017Q3: Foundations Team added

#9 Updated by intrigeri 2017-08-30 07:01:51

Subject changed from Consider basing Tails on quarterly snapshots of Debian Testing to Consider basing Tails on quarterly snapshots of Debian testing

#10 Updated by intrigeri 2017-08-30 07:46:47

Blueprint changed from https://tails.boum.org/blueprint/Debian_Stretch/#rolling to https://tails.boum.org/blueprint/Debian_testing/

#11 Updated by intrigeri 2017-08-30 07:48:02

Dumped & organized what we discussed & decided at the summit into a new blueprint. Keeping this assigned to me for 3.2 in order to schedule the first sprints.

#12 Updated by intrigeri 2017-09-01 13:37:04

Target version changed from Tails_3.2 to Tails_3.3

(The work we’ve scheduled will start after the 3.2 release.)

#13 Updated by intrigeri 2017-09-24 09:40:56

blocks ~~Feature #13244~~: Core work 2017Q4: Foundations Team added

#14 Updated by intrigeri 2017-09-24 09:41:37

blocked by deleted (~~~~Feature #13234~~: Core work 2017Q3: Foundations Team~~)

#15 Updated by intrigeri 2017-09-28 05:52:45

related to ~~Bug #14622~~: Have the Installer detect when "Clone the current Tails" won't fit in the destination partition before deleting anything added