- From: Drew Powers via GitHub <sysbot+gh@w3.org>
- Date: Thu, 24 Oct 2024 20:24:10 +0000
- To: public-design-tokens-log@w3.org
> +1 to letting this be solved by tools in `$extensions` or git or underlying database - no need for an additional status or state. I agree with this—embedding history into the spec like this would balloon into quickly-unmanageable filesizes for larger design systems. Plus it would likely be limiting in many ways, since many concepts of versioning won’t ever map 1:1 with tokens (e.g. tokens will get deleted/merged/mutated in ways that will make a simple linear history difficult to trace). Plus, may design systems may want to define their own set of versioning principles, and come up with their own “changelogs” as they see fit, without restrictions. I am in favor of the underlying `$deprecated` proposal because there is sufficient prior art there. But for versioning/auditing, this feels more deferring to Git or other existing protocols for this would be ideal. -- GitHub Notification of comment by drwpow Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/161#issuecomment-2436273447 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 24 October 2024 20:24:11 UTC