- From: Adrian Secord via GitHub <sysbot+gh@w3.org>
- Date: Tue, 12 Jul 2022 16:23:38 +0000
- To: public-design-tokens-log@w3.org
For communication in long-running projects, `deprecated` is so useful as to be required, I think. It gives the authors the flexibility to change things without breaking all downstream users immediately. We also use a `replacement`-like field both for concise communication (in addition to the deprecation message) and tooling support. Re: encoding something like `Experimental → Active → Deprecated → Sunset → Deleted` in the spec: this is brittle because different teams have (sometimes very) different ideas of what the right life cycle states should be. If we go this way, the states will need to be configurable and not fixed. -- GitHub Notification of comment by ajsecord Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/118#issuecomment-1181981311 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 12 July 2022 16:23:40 UTC