-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Add more clarity on when the urgent label can be applied #53
Conversation
We should only be using "urgent" if the break was within that last 72 hours, i.e. not for something that has been broken for weeks.
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.
LGTM
LGTM. |
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.
Wording seems fine to me.
Fixup pushed incorporating the suggested wording updates. Please take another look. |
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.
LGTM
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.
Looks good to me
Vote: +1 |
I'm calling this PR to OMC vote: As per the recommendation of the Working Group, the OMC to accept the change to the committer policy in PR#53 as of commit a762499 |
Vote [+1] |
1 similar comment
Vote [+1] |
Voting +1
|
Vote: +1 |
1 similar comment
Vote: +1 |
The vote was closed and passed:
Pushed. |
We should only be using "urgent" if the break was within that last 72 hours, i.e. not for something that has been broken for weeks.