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:
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information