-
Notifications
You must be signed in to change notification settings - Fork 6.1k
Update EIP statuses #3096
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
Update EIP statuses #3096
Conversation
|
Going to merge this since we have already discussed it at length and I suspect (based on history) no one else will comment. It touches fairly few files, so if we decide we want to rollback later we can pretty easily. |
|
Oops, just after clicking merge I realized that |
|
Are we not using Stagnant anymore? Because |
|
I believe we only had Abandoned previously, and I believe that previous to now we have never marked an EIP as Abandoned except when the author requested/supported it. Would probably be valuable to go through and check the PRs that changed each of these to Abandoned and verify that is the case though. |
|
I just verified all of them were moved to Abandoned by the author, so I believe Withdrawn is correct here. |
|
I guess my understanding if ProgPow's status was that it was fully specified and ready to be included in a hard fork if it were decided by the core developers necessary. In which case, I believe the appropriate status is |
|
I'm really hesitant to automatically move anyone's EIP into Final without their consent, since they lose the ability to make normative changes at that point. |
|
Yeah, I think |
I'm updating EIP statuses according to ethereum#2996. The mappings are as follows: ``` Draft => Draft Last Call => Last Call Accepted => Final Final => Final Superseded => Final Abandoned => Withdrawn Rejected => Withdrawn Active => Living ```
I'm updating EIP statuses according to #2996. The mappings are as follows: