Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 974
    • Issues 974
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 35
    • Merge requests 35
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #12615
Closed
Open
Issue created May 30, 2017 by intrigeri@intrigeriMaintainer

Consider basing Tails on quarterly snapshots of Debian testing

Originally created by @intrigeri on #12615 (Redmine)

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.

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

Attachments

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

Subtasks

  • #12690 (closed)
  • #12691 (closed)
  • #14514 (closed)
  • #14577 (closed)
  • #14578 (closed)
  • #14579 (closed)
  • #14791 (closed)
  • #14814 (closed)
  • #14823 (closed)

Related issues

  • Related to #14622 (closed)
  • Related to #11881 (closed)
Edited May 21, 2020 by intrigeri
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking