- From: Jeffrey Yasskin via GitHub <sysbot+gh@w3.org>
- Date: Tue, 05 Mar 2024 18:08:30 +0000
- To: public-css-archive@w3.org
I don't have a good answer for you. Back in the day, there were documents like https://www.w3.org/TR/qaframe-spec/ that specified how to write specifications, but I don't think we have that sort of meta-WG right now in any of the standards bodies I follow. Instead, we have statements like https://whatwg.org/working-mode#removals that defer to implementer opinions, and https://www.chromium.org/blink/launching-features/#feature-deprecations that governs how Chrome in particular makes this sort of decision. The AB might be an appropriate body to think about this at the W3C-wide level, since they have an [Incubation](https://www.w3.org/wiki/AB/2024_Priorities#Incubation) activity considering the other end of the pipeline. You can suggest they look at breaking changes by filing an issue in https://github.com/w3c/AB-public/issues. The CSSWG could also create an opinion for itself, but that wouldn't advise any other WGs. -- GitHub Notification of comment by jyasskin Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5165#issuecomment-1979349809 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 5 March 2024 18:08:31 UTC