Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 974
    • Issues 974
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 26
    • Merge requests 26
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • 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
  • #12152
Closed
Open
Issue created Jan 17, 2017 by Anonymous@Anonymous

Update tails-installer release process

Originally created by @Anonymous on #12152 (Redmine)

In #8549 (closed) we discussed that updating tails-installer for every Tails release might now not be necessary anymore. I think we still need to update the RM release process and documentation with this new information.
Maybe we also need to define how it will happen instead?
Or do we simply maintain things as they are currently - that is now the RM can push to pkg-privacy? Should bertagaz also be added to pkg-privacy then?

Related issues

  • Related to #8549 (closed)
  • Related to #15533 (closed)
  • Blocks tails/accounting#15139
Edited May 15, 2020 by Anonymous
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking