vacp2p
/
unprotocols-rfc
mirror of https://github.com/vacp2p/unprotocols-rfc.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Problem: COSS doesn't articulate application of cosmetic changes 

Solution: indicate that cosmetic changes ot Stable specifications
are permitted
This commit is contained in:
Yurii Rashkovskii 2016-06-02 06:59:39 +07:00
parent c29de510ca
commit 7428994d9e
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
2/README.md
View File

@ -86,7 +86,7 @@ All new specifications are **raw** specifications. Changes to raw specifications
When raw specifications can be demonstrated, they become **draft** specifications. Changes to draft specifications should be done in consultation with users. Draft specifications are contracts between the editors and implementers. When raw specifications can be demonstrated, they become **draft** specifications. Changes to draft specifications should be done in consultation with users. Draft specifications are contracts between the editors and implementers.
### Stable Specifications ### Stable Specifications
When draft specifications are used by third parties, they become **stable** specifications. Changes to stable specifications should be restricted to errata and clarifications. Stable specifications are contracts between editors, implementers, and end-users. When draft specifications are used by third parties, they become **stable** specifications. Changes to stable specifications should be restricted to cosmetic ones, errata and clarifications. Stable specifications are contracts between editors, implementers, and end-users.
### Deprecated Specifications ### Deprecated Specifications