-
Notifications
You must be signed in to change notification settings - Fork 17
Issue Labels #7
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
Comments
I think that's a great idea. Go ahead and create such labels.
…On Tue, Oct 15, 2019, at 9:41 PM, Zach Jibben wrote:
Should we have labels for stages of various issues? The readme suggests we'll be tracking proposals through to final standardization, or rejection. Labels along the lines of "unsubmitted", "accepted", "rejected", "under consideration", "on hold", and maybe "in progress" would help organize this. And perhaps a "meta" label for issues related to this repo. I imagine "accepted" and "rejected" labels would only be used for closed issues.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#7>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAFAWGF4PF42ZOAWBHYECTQO2LP3ANCNFSM4JBGCBGA>.
|
I added labels and assigned them to existing issues, feel free to modify as needed. |
What does "unsubmitted" mean? |
@pdebuyl I just added a remark for the label ("Has not been submitted to the committee yet"). |
You might want to pin this issue; or a similar one discussing labeling. |
Now that we have the meta label, we don't need [META] in meta issue titles, correct? I did some tidying up with meta labels, then stumbled upon this. I'll revert if you disagree. |
That's fine with me, you can remove the [META] label. |
What about adding labels for different types of proposals (i.e. 'syntactic sugar', 'C interoperability', 'coding convention', 'efficiency improvement', 'new feature', 'enhanced feature'...)? In a way, this has already been done with the 'meta' label. |
We have issue labels now, so I am going to close this issue. |
Should we have labels for stages of various issues? The readme suggests we'll be tracking proposals through to final standardization, or rejection. Labels along the lines of "unsubmitted", "accepted", "rejected", "under consideration", "on hold", and maybe "in progress" would help organize this. And perhaps a "meta" label for issues related to this repo. I imagine "accepted" and "rejected" labels would only be used for closed issues.
The text was updated successfully, but these errors were encountered: