- From: Joshua Lindquist via GitHub <sysbot+gh@w3.org>
- Date: Fri, 06 Mar 2020 15:07:26 +0000
- To: public-css-archive@w3.org
> 1. Major version number changes when something believed to be a big deal or game changer. Usually something that required major javascript hacks to work (which probably didn't always work) and/or are too complex to be implemented reliably as polyfills or shims. > > 2. Minor version changes when a set of welcome features are released. These are usually some new attribute values or a small set of cosmetic attributes people will feel pleased to use because, due to them, less "HTML hacking" is required to get things done. > This sounds very hard to do as a way to number the releases. I don't know if it would solve the current concern of CSS feeling slow-to-change or needing a marketing push. Among your own examples, you have separated the same property into different types of versions with two values of `display` falling into #1 while another value of display is considered #2. I like the idea of focusing on specific features instead of complete specifications. It just seems hard to separate them all into different buckets of "importance" (which is subjective). -- GitHub Notification of comment by JoshuaLindquist Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4770#issuecomment-595809678 using your GitHub account
Received on Friday, 6 March 2020 15:07:27 UTC