-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ZEP0001 status clarification, not "Final"? #265
Comments
@MSanKeys963 , ping. Could you clarify the current state. |
Hi @mkitti. 👋🏻
Yes! As discussed in the last ZEP meeting (rolling notes here), the ZEP0001 is currently The ZIC are currently in the implementation phase, and we're in a grace period (which will end soon) to accept minor changes to the specification. Once we're sure that the implementors propose no additional changes, we will do a quick round of voting, and after that ZEP0001 will be I hope that helps. Please let me know if there's anything else. |
Closing this now. |
With the caveat, @MSanKeys963, that explanations like the above should be backported to ZEP0000 itself. |
#260 and #261 marked ZEP0001 as
Accepted
.ZEP0000 suggests that the status should now be
Final
.However, #263 and #264 seem to be approaching ZEP0001 as if it were
Provisionally Accepted
which is a state which is not supposed to apply to "core" specifications.What kind of changes are permitted to ZEP0001 when it is
Accepted
but not yetFinal
? When does ZEP0001 becomeFinal
? Are (minor) breaking changes are permitted in theFinal
state?The text was updated successfully, but these errors were encountered: