Add Updates section to top level README #891
Merged
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.
After consideration in #887 (comment) — for increased visibility in the community, especially to attract attention from stakeholders & implementors for any affected CIPs.
This uses a low bar for query compared to the Candidate list: only querying the
Update
tag without checking for a reviewState:
tag... relying on that one bit of editor confirmation to keep spam or inappropriate update requests from being linked from the front page.I don't see the harm in including likely "abandoned" or "deprecated"
Update
PR's here... in fact I believe it's important to include them because CIP/CPS updates aren't included in the Stalled / Waiting For Authors list (since the latter is only for new CIPs/CPSs).(newly added section, rendered in branch)