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 944
    • Issues 944
    • 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
  • #16585

Closed
Open
Opened Mar 21, 2019 by Cyril 'kibi' Brulebois@CyrilBrulebois

release_process: add intermediary “update misc files” commit?

Originally created by @CyrilBrulebois on #16585 (Redmine)

Currently there are a lot of things getting done post release, under “Rename, copy, garbage collect and update various files”.

The first git commit instructions is very much below, after having collected things for the news about security bugfixes, etc.

I’d be happy to have two additions here:

  • mentioning cleaning up GPG’s output, which can (and at least locally always do) contain warnings about key trust.
  • a call to git add and git commit with e.g. “Update misc files for ${VERSION?:}”

so that it can be recorded properly in git before new files get added with changelog excerpts/security fixes, etc.

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