- From: Daniel Hruška via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 May 2024 12:42:24 +0000
- To: public-design-tokens-log@w3.org
How do we define upfront how the spec will evolve? In my opinion being in IT for more than a decade, maintaining absolute backwards compatibility is hard. I would aim for "loose" backwards compatibility as long as possible. When a reason for new major spec is needed, let's 1. Declare "version 3.0 is not compatible with 2.8 and older" 2. Show the benefits 3. Document the changes so anyone can reflect them in their tools 4. (Nice-to-have) Publish a translation tool for `.tokens.json` files so everyone could update them -- GitHub Notification of comment by danosek Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/162#issuecomment-2139472707 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 30 May 2024 12:42:25 UTC