Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
T
tails
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 947
    • Issues 947
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 13
    • Merge Requests 13
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • tails
  • tails
  • Issues
  • #17911

Closed
Open
Opened Sep 02, 2020 by anonym@anonymMaintainer

Maybe calm down with kernel upgrades?

After attending a Frontdesk meeting it was made very clear to me that #17834 (closed) was a major pain for users. The Frontdesk team is worried that we are moving too fast with kernel updates.

I think it might be worth revisiting our guidelines for kernel upgrades, and perhaps do a blameless post-mortem of #17786 (closed) where we proceeded with the kernel upgrade to 5.7.0-1 despite knowing about this regression. Perhaps we want to switch to another model, for instance, to skip the x.y.0-1 kernels and wait for the x.y.0-2 or higher when the some of the more painful regressions are fixed, although that would makes us lag on security fixes since we use Sid kernels => there are no backported security fixes.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tails_4.11
Milestone
Tails_4.11 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: tails/tails#17911