- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Fri, 14 Feb 2020 20:45:55 +0000
- To: public-css-archive@w3.org
@bkardell Calling the next collection of modules CSS4 has a few benefits over year names: - Builds on existing familiarity with idea of CSS1, CSS3, CSS3 - Doesn't set up an expectation for yearly releases or get mixed up with the year-based spec-maturity ["Snapshots"](https://www.w3.org/TR/CSS/) - Allows us to build up and talk about CSS.next without trying to guess when we close its definition. - Doesn't label the collection of technology with particular timing, allowing developers, who (as Rachel points out) have different ideas of when something is sufficiently mature to become relevant to their work, to decide what year it's "ready" for them. -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4770#issuecomment-586465968 using your GitHub account
Received on Friday, 14 February 2020 20:45:57 UTC