CSSDB: 6.0.0

.gitignore

@@ -3,3 +3,4 @@ node_modules
 dist
 public/images/badges
 cssdb.mjs
+cssdb.json

CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changes to cssdb
 
+### 6.0.0
+
+- Exported CSSDB no longer exposes example or `caniuse-compat` (breaking)
+- Stage is now calculated from a mix of Spec status and Engine implementation (breaking)
+
 ### 5.0.0 (May 24, 2019)
 
 - Removed: Rejected `:matches()` psuedo-class (major)

STAGES.md

@@ -13,16 +13,18 @@ features developed outside the [W3C] have appeared in browsers. This is too
 ambiguous for the web development community, and a more accountable process
 is desired.
 
+Our staging process tries to faithfully picture the feature's support both in 
+terms of vendor implementation and spec progress.
+
 ### Stage 0: Aspirational
 
 <img src="https://cssdb.org/images/stages/stage-0.svg" alt="" align="left" width="90" height="90">
 
 > “This is a silly idea.”
 
 An **Unofficial Draft** or **Editor’s Draft** [championed] by a
-[W3C Working Group] Member. It should be considered highly unstable and subject
-to change. Stage 0 features are open to ideas and discussion, but may not be
-considered serious.
+[W3C Working Group] Member or implemented by less than two [recognized browser vendors]. It should be considered highly unstable and subject to change. This feature should be considered highly unstable and subject to change.
+Polyfill authors and users should expect significant changes to their codebase as the specification evolves.
 
 ---
 
@@ -33,9 +35,9 @@ considered serious.
 > “This idea might not be silly.”
 
 An **Editor’s Draft** or early **Working Draft** [championed] by a
-[W3C Working Group]. It should be considered highly unstable and subject to
-change. Stage 1 features are recognized as a real problem, but they may not be
-tied to any particular solution.
+[W3C Working Group] or implemented by less than two browser engines. It should be considered highly unstable and subject to change. Stage 1 features are recognized as a real problem, but they may not be
+tied to any particular solution. This feature should be considered highly unstable and subject to change.
+Polyfill authors and users should expect significant changes to their codebase as the specification evolves.
 
 ---
 
@@ -45,9 +47,8 @@ tied to any particular solution.
 
 > “This idea is not silly.”
 
-A **Working Draft** [championed] by a [W3C Working Group]. It should be
-considered relatively unstable and subject to change. Stage 2 features are tied
-to a particular way of solving a problem.
+A **Working Draft** [championed] by a [W3C Working Group] or implemented by at least two [recognized browser vendors]. It should be considered relatively unstable and subject to change. Stage 2 features are tied to a particular way of solving a problem. This feature should be considered somewhat unstable and subject to change.
+Polyfill authors and users could experience changes to their codebase as the specification evolves.
 
 ---
 
@@ -57,10 +58,9 @@ to a particular way of solving a problem.
 
 > “This idea is becoming part of the web.”
 
-A **Candidate Recommendation** [championed] by a [W3C Working Group], usually
-implemented by at least 2 [recognized browser vendors], possibly behind a flag. |
-It should be considered stable and subject to little change. Stage 3 features
-will likely become a standard.
+A **Candidate Recommendation** [championed] by a [W3C Working Group] or implemented by at least 3 [recognized browser vendors], possibly behind a flag. It should be considered stable and subject to little change. Stage 3 features
+will likely become a standard. This feature should be considered somewhat stable but subject to change.
+Polyfill authors and users might experience minor changes to their codebase as the specification evolves.
 
 ---
 
@@ -70,8 +70,7 @@ will likely become a standard.
 
 > “This idea is part of the web.”
 
-A **Recommendation** [championed] by the [W3C]. It should be implemented by all
-[recognized browser vendors]. Stage 4 features are web standards.
+A **Recommendation** [championed] by the [W3C]. It should be implemented by all [recognized browser vendors]. Stage 4 features are web standards.
 
 ---
 
@@ -90,8 +89,7 @@ formally rejected by a [W3C Working Group].
 
 ### Recognized Browser Vendors
 
-Recognized browser vendors include, in alphabetical order; Apple, Google,
-Microsoft, Mozilla, and Opera.
+Recognized browser vendors include, in alphabetical order; Apple, Google and Mozilla.
 
 ### What is a champion?