diff options
| author | Karel Zikmund <karelz@microsoft.com> | 2017-06-09 02:22:13 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-06-09 02:22:13 +0300 |
| commit | fd60590b54e0d1faa37745e4cb405284542020e0 (patch) | |
| tree | 17198d02279de200d92603d3d0aa2aaf673b0e79 /Documentation | |
| parent | 10b35fa837ff486358c234f667c34575d86b6c37 (diff) | |
Create issue-guide.md
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/project-docs/issue-guide.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/Documentation/project-docs/issue-guide.md b/Documentation/project-docs/issue-guide.md index f22bcd47e8..b4608cf754 100644 --- a/Documentation/project-docs/issue-guide.md +++ b/Documentation/project-docs/issue-guide.md @@ -132,8 +132,9 @@ Feel free to use other labels if it helps your triage efforts (e.g. **needs more * Movitation: Area owners will get email notification about new issue in their area. 1. PR has **Assignee** set to author of the PR, if it is non-CoreFX engineer, then area owners are co-assignees * Motivation: Area owners are responsible to do code reviews for PRs from external contributors. CoreFX engineers know how to get code reviews from others. -1. Set milestone according to the branch (master = 2.1, release/2.0.0 = 2.0, release/1.0.0 = 1.0.x, release/1.1.0 = 1.1.x) +1. [Optional] Set milestone according to the branch (master = 2.1, release/2.0.0 = 2.0, release/1.0.0 = 1.0.x, release/1.1.0 = 1.1.x) * Motivation: Easier to track where which fix ended and if it needs to be ported into another branch + * Note: This is easily done after merge via simple queries & bulk-edits, you don't have to do this one. 1. Any other labels on PRs are superfluous and not needed (exceptions: **blocked**, **NO MERGE**) * Motivation: All the important info (*issue type* label, api approval label, OS label, etc.) is already captured on the associated issue. 1. Push PRs forward, don't let them go stale (response every 5+ days, ideally no PRs older than 2 weeks) |