Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #30704

Closed (moved)
Open
Opened May 30, 2019 by Cecylia Bocovich@cohosh

Plan for snowflake update versioning and backwards compatability

We have some upcoming changes that will change the way snowflake components talk to each other. We should decide (and possibly on a case-by-case basis) how to handle these updates.

  • Do we make sure changes are backwards compatible with clients/proxies that haven't updated yet?
  • Should we think about introducing some concept of versioning?
  • If we support older versions, how long until we no longer support them?

Some examples of tickets that we'll need to think about this for:

  • #25429 (moved)
  • #29206 (moved)
  • #29207 (moved)
  • #25985 (moved)
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#30704