-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
Close a few more issues #5119
Comments
I don't consider #4917 to be stale yet, and I do think an issue in this repository is the correct place for such discussion (changes to the EIP process). |
Regarding the last set, we need to discuss this more. Our current policy is that issues as discussions-to links can be grandfathered in, and we don't have a long term strategy for migrating that content elsewhere. We have talked in the past about closing the discussions-to issues for EIPs that reach final, stagnant, or withdrawn which would help in a lot of these cases but I don't think we ever came to agreement on that process. This would be good to discuss further in the EIP meeting. |
I think we should grab all the issues, copy-paste them to ethereum magicians, and close the issues. |
Exactly my idea. Must've forgotten to put it in the actual issue itself. |
I have updated the issue, specifying the status of the respective EIP. |
This comment was marked as resolved.
This comment was marked as resolved.
Superseded by #5127 |
No EIP with discussion-to linked to issue (should be closed immediately as there is no EIP for them to be grandfathered in to):
Final EIPs (should be closed):
Withdrawn EIPs (should be closed):
Stagnant EIPs (should be closed as not implemented, can be reopened):
Last Call (should be merged as final):
Draft EIPs (no action needed imminently, should be transferred to eth magicians):
Review EIPs (no action needed imminently, should be transferred to eth magicians):
The text was updated successfully, but these errors were encountered: