1.1.2 Stability Index
| Topic Version | 1 | Published | 10/31/2016 | |
| For Standard | ETP v1.1 | |||
Chapter 3 of this document indicates the stability of each ETP protocol, using values described in the table below. This concept of assigning a stability index was borrowed from the Node.js API and is intended to allow evolutionary development of the specification, while allowing implementers to use with confidence the portions that are stable. ETP is still changing, and as it matures, certain parts are more reliable than others.
|
Index No. |
Status |
Description |
|---|---|---|
|
0 |
Deprecated |
This feature is known to be problematic and changes are planned. Do not rely on it. Use of the feature may cause warnings. Backwards compatibility should not be expected. |
|
1 |
Experimental |
This feature was introduced recently and may change or be removed in future versions. Please try it out and provide feedback. If it addresses a use case that is important to you, tell the core team. |
|
2 |
Unstable |
The API is in the process of settling but has not yet had sufficient real-world testing to be considered stable. Backwards compatibility will be maintained, if reasonable. |
|
3 |
Stable |
The API has proven satisfactory, new features will not be added. Backwards compatibility is guaranteed, unless a critical issue is found. |
|
4 |
Locked |
The API will not change. Please do not suggest changes in this area; they will be refused. |