From 2b817c844722c6578d9914a4809556bb883e360b Mon Sep 17 00:00:00 2001 From: Tim Beiko Date: Fri, 22 Mar 2019 11:21:45 -0400 Subject: [PATCH 1/2] Make "Accepted" definition consistent for Core EIPs The previous version of EIP-1 had two conflicting definitions of what "Accepted" meant for Core EIPs. This harmonizes them. --- EIPS/eip-1.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/EIPS/eip-1.md b/EIPS/eip-1.md index 8fc28d16cb96f..85661be944424 100644 --- a/EIPS/eip-1.md +++ b/EIPS/eip-1.md @@ -58,11 +58,11 @@ Each status change is requested by the EIP author and reviewed by the EIP editor * :x: Last Call -- A request for Last Call status will be denied if material changes are still expected to be made to the draft. We hope that EIPs only enter Last Call once, so as to avoid unnecessary noise on the RSS feed. * **Last Call** -- This EIP will listed prominently on the https://eips.ethereum.org/ website (subscribe via RSS at [last-call.xml](/last-call.xml)). * :x: -- A Last Call which results in material changes or substantial unaddressed technical complaints will cause the EIP to revert to Draft. - * :arrow_right: Accepted (Core EIPs only) -- A successful Last Call without material changes or unaddressed technical complaints will become Accepted. + * :arrow_right: Accepted (Core EIPs only) -- This EIP is in the hands of the Ethereum client developers. * :arrow_right: Final (Not core EIPs) -- A successful Last Call without material changes or unaddressed technical complaints will become Final. * **Accepted (Core EIPs only)** -- This EIP is in the hands of the Ethereum client developers. Their process for deciding whether to encode it into their clients as part of a hard fork is not part of the EIP process. * :arrow_right: Final -- Standards Track Core EIPs must be implemented in at least three viable Ethereum clients before it can be considered Final. When the implementation is complete and adopted by the community, the status will be changed to “Final”. -* **Final** -- This EIP represents the current state-of-the-art. A Final EIP should only be updated to correct errata. +* **Final (Not core EIPs)** -- This EIP represents the current state-of-the-art. A Final EIP should only be updated to correct errata. Other exceptional statuses include: From 470eb5685cf59dd7e3e69243a8d8bdf9aef896ee Mon Sep 17 00:00:00 2001 From: Tim Beiko Date: Wed, 27 Mar 2019 09:32:16 -0400 Subject: [PATCH 2/2] Removed `(Non Core EIPs)` from `Final` --- EIPS/eip-1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-1.md b/EIPS/eip-1.md index 85661be944424..1a60ff72a271d 100644 --- a/EIPS/eip-1.md +++ b/EIPS/eip-1.md @@ -62,7 +62,7 @@ Each status change is requested by the EIP author and reviewed by the EIP editor * :arrow_right: Final (Not core EIPs) -- A successful Last Call without material changes or unaddressed technical complaints will become Final. * **Accepted (Core EIPs only)** -- This EIP is in the hands of the Ethereum client developers. Their process for deciding whether to encode it into their clients as part of a hard fork is not part of the EIP process. * :arrow_right: Final -- Standards Track Core EIPs must be implemented in at least three viable Ethereum clients before it can be considered Final. When the implementation is complete and adopted by the community, the status will be changed to “Final”. -* **Final (Not core EIPs)** -- This EIP represents the current state-of-the-art. A Final EIP should only be updated to correct errata. +* **Final** -- This EIP represents the current state-of-the-art. A Final EIP should only be updated to correct errata. Other exceptional statuses include: