#30704: Plan for snowflake update versioning and backwards compatability -----------------------------------------+-------------------- Reporter: cohosh | Owner: (none) Type: task | Status: new Priority: Medium | Milestone: Component: Circumvention/Snowflake | Version: Severity: Normal | Keywords: Actual Points: | Parent ID: Points: | Reviewer: Sponsor: | -----------------------------------------+-------------------- 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 - 29206 - #25985 -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30704> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs