-
-
Notifications
You must be signed in to change notification settings - Fork 36
Add proposed/accepted status to design docs #461
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But otherwise ready...
Co-authored-by: Addison Phillips <addisonI18N@gmail.com>
Requesting fast-tracking. |
In my mind, a design doc would only be merged into |
@stasm Could you review #458, as that's effectively the prototypical reason for this change? It's currently at 35 comments in 13 threads of review comments, most of which are hidden as resolved. If we don't make this change, we won't be able to merge the PR until all expression attribute design questions are answered, including e.g. whether it's the proper vessel for communicating "open" vs. "closed" concepts which have not yet been mentioned at all. |
We should track and signal the status of a design document, so that we can iterate on them across multiple PRs. To keep it simple, we probably don't need more than two statuses to start with, "proposed" and "accepted".
CC @ryzokuken, who also has a design doc PR in flight.