Update EEP statuses #52
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
erszcz
reviewed
Sep 6, 2023
williamthome
reviewed
Sep 7, 2023
|
@williamthome: I'd say Post-History is a field that is not very important, and often hard to use as originally intended. The original intention, as per EEP 1 was to document when the topic was discussed on erlang-questions, an EEP was was supposed discussed before being submitted so there should only be left to approve or reject it. It has turned out to be more common to write an EEP and then the discussion is about the content. I'd say this is a more reasonable process... So we could redesign how the Post-History field should be used, and/or not use it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #48