Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #20828

Closed (moved)
(moved)
Open
Created Nov 29, 2016 by Nick Mathewson@nickm🍬

Should we provide a migration method from the old guard logic to the new one?

Our new (prop271) guard code stores guard state in a new way, and makes no effort to look at the old guard state. For clients who are upgrading, should we put more effort into keeping their pre-0.3.0 guards? We need to decide soon.

(I lean towards "no".)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking