We observe that specs mature in sub-stages that roughly map to the W3C process.
|Exploring||The spec is incomplete, rapidly changing, and might include many features that will be dropped later.||pre-FPWD and early WD|
|Revising||The module is mostly complete and has a well-defined scope. The spec will go through several rounds of revisions still.||mid-stage WD|
|Stabilizing||Spec is fairly stable at this point. Only minor polishing and LC comments are left. New feature suggestions are deferred to the next level.||late-stage WD|
|Call for Implementations||Spec is considered complete. While experimental implementations were welcome before, at this point implementations are officially requested for feedback. Testsuites are written here.||early CR|
|Recommended||Spec is considered stable and ready for wide use, though testing may not yet be complete, and minor issues might still come in for handling. To indicate this stage, we put the spec in our CSS Snapshot.||late CR|
|Finished||Spec is done and enters maintenance mode. The only changes at this stage are errata.||PR, REC|
Goal: specification is demonstrated to be stable via implementation and testing experience
100% not yet completed, but no further changes expected, just like REC. Authors and new implementors can rely on for production use, just like REC.
|Exploring||Whiteboard drawings and discussions!||pre-FPWD and early WD|
|Revising||Pre-alpha (prototyping)||mid-stage WD|
|Stabilizing||Alpha (bleeding edge)||late-stage WD|
|Call for Implementations||Beta (ready for early adoption)||early CR|
|Recommended||x.0 Release (ready for everyone)||Snapshot CR|
|Finished||x.1 Release (last bugs fixed)||PR, REC|