+-------+-----------+----------------------------------------+
| stage | name      | mission                                |
+-------+-----------+----------------------------------------+
| 0     | strawman  | Present a new feature (proposal)       |
|       |           | to TC39 committee. Generally presented |
|       |           | by TC39 member or TC39 contributor.    |
+-------+-----------+----------------------------------------+
| 1     | proposal  | Define use cases for the proposal,     |
|       |           | dependencies, challenges, demos,       |
|       |           | polyfills etc. A champion              |
|       |           | (TC39 member) will be                  |
|       |           | responsible for this proposal.         |
+-------+-----------+----------------------------------------+
| 2     | draft     | This is the initial version of         |
|       |           | the feature that will be               |
|       |           | eventually added. Hence description    |
|       |           | and syntax of feature should           |
|       |           | be presented. A transpiler such as     |
|       |           | Babel should support and               |
|       |           | demonstrate implementation.            |
+-------+-----------+----------------------------------------+
| 3     | candidate | Proposal is almost ready and some      |
|       |           | changes can be made in response to     |
|       |           | critical issues raised by adopters     |
|       |           |  and TC39 committee.                   |
+-------+-----------+----------------------------------------+
| 4     | finished  | The proposal is ready to be            |
|       |           | included in the standard.              |
+-------+-----------+----------------------------------------+