- From: Mathieu Dutour via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Jan 2020 16:16:02 +0000
- To: public-design-tokens-log@w3.org
> the token's status is something that I believe can and should be standardized Should it? A status seems arbitrary and dependent on the workflow of a team (eg. release cycle, etc.). What does "deprecating a token" means? "Will be removed in the next version" (that's the common definition for "deprecating" something in the software world? But then that implies a version? I'd be wary to add stuff to the specs too fast as it's always easy to add stuff later but much harder to remove stuff (except if we want some deprecation warning on the spec 😄 ) -- GitHub Notification of comment by mathieudutour Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/1#issuecomment-580330905 using your GitHub account
Received on Thursday, 30 January 2020 16:16:05 UTC