From: Karel Zikmund Date: Thu, 1 Aug 2019 15:42:09 +0000 (+0200) Subject: Update issue-guide.md X-Git-Tag: submit/tizen/20210909.063632~11031^2~793 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=acd8190eab1f6f114fbb5b0de0b8c13c48fa265d;p=platform%2Fupstream%2Fdotnet%2Fruntime.git Update issue-guide.md Commit migrated from https://github.com/dotnet/corefx/commit/83143cd0170770997a83b6543e406b5bf0db7d0a --- diff --git a/docs/libraries/project-docs/issue-guide.md b/docs/libraries/project-docs/issue-guide.md index 8beae5f..63eb7eb 100644 --- a/docs/libraries/project-docs/issue-guide.md +++ b/docs/libraries/project-docs/issue-guide.md @@ -148,7 +148,8 @@ Feel free to use other labels if it helps your triage efforts (e.g. **needs more 1. Each PR has exactly one **area-\*** label * 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. + * Motivation #1: Area owners are responsible to do code reviews for PRs from external contributors. CoreFX engineers know how to get code reviews from others. + * Motivation #2: Assignees will get notifications for anything happening on the PR. 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.