Project

General

Profile

Feature #12615

Consider basing Tails on quarterly snapshots of Debian testing

Added by intrigeri 5 months ago. Updated about 13 hours ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
06/13/2017
Due date:
08/21/2017
% Done:

63%

QA Check:
Feature Branch:
Type of work:
Research

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:

  1. 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 :)
  2. 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.

gitstats-2.x-to-3.0.tar.bz2 (202 KB) intrigeri, 06/13/2017 09:03 AM


Subtasks

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

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

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

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

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

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

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

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

Feature #14823: Simulate tracking of security updates on a frozen Buster stable branch between Buster sprint #1 and #2Confirmedintrigeri


Related issues

Related to Tails - Bug #14622: Have the Installer detect when "Clone & Upgrade" won't fit in the destination partition before deleting anything Confirmed 09/11/2017
Blocks Tails - Feature #13244: Core work 2017Q4: Foundations Team Confirmed 06/29/2017

Associated revisions

Revision fd215ee3 (diff)
Added by intrigeri 4 months ago

Initial analysis of the porting to Stretch (refs: #12615).

Revision 3a5cfc28 (diff)
Added by intrigeri about 2 months ago

Document plans for basing Tails on Debian testing (refs: #12615).

History

#1 Updated by intrigeri 4 months ago

  • Description updated (diff)

#2 Updated by intrigeri 4 months ago

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

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

#3 Updated by intrigeri 4 months ago

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

#4 Updated by intrigeri 4 months ago

#5 Updated by intrigeri 4 months ago

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

intrigeri wrote:

  1. 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 4 months ago

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

#7 Updated by intrigeri 4 months ago

  • 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 4 months ago

#9 Updated by intrigeri about 2 months ago

  • 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 about 2 months ago

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

#11 Updated by intrigeri about 2 months ago

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 about 2 months ago

  • 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 27 days ago

#14 Updated by intrigeri 27 days ago

#15 Updated by intrigeri 23 days ago

  • Related to Bug #14622: Have the Installer detect when "Clone & Upgrade" won't fit in the destination partition before deleting anything added

#16 Updated by intrigeri about 13 hours ago

  • Target version changed from Tails_3.3 to Tails_3.4

Also available in: Atom PDF