Update EIP-1: Semi-stagnation of last call EIPs #7346
Conversation
…-call-deadline passes
| @@ -79,15 +79,15 @@ The following is the standardization process for all EIPs in all tracks: | |||
|
|
|||
| **Review** - An EIP Author marks an EIP as ready for and requesting Peer Review. | |||
|
|
|||
| **Last Call** - This is the final review window for an EIP before moving to `Final`. An EIP editor will assign `Last Call` status and set a review end date (`last-call-deadline`), typically 14 days later. | |||
| **Last Call** - This is the final review window for an EIP before moving to `Final`. An EIP editor will assign `Last Call` status and set a review end date (`last-call-deadline`), typically 14 days later. If 6 months pass after the `last-call-deadline`, it is moved back into `Review`. | |||
There was a problem hiding this comment.
Should we move it to Stagnant directly?
There was a problem hiding this comment.
Last call should imply some degree of community participation. If you want, this time can be reduced down to e.g. one month. But -1 to moving directly to Stagnant.
|
There has been no activity on this pull request for 2 weeks. It will be closed after 3 months of inactivity. If you would like to move this PR forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review. |
|
There has been no activity on this pull request for 2 weeks. It will be closed after 3 months of inactivity. If you would like to move this PR forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review. |
|
This pull request was closed due to inactivity. If you are still pursuing it, feel free to reopen it and respond to any feedback or request a review in a comment. |
Fixes #7328
Note that the stagnant bot does NOT touch Last call EIPs, which is technically not in line with the current EIP-1.
I am working on a new and improved stagnant bot.