HOWTO review backport PRs » History » Version 1
Nathan Cutler, 08/10/2016 06:43 PM
| 1 | 1 | Nathan Cutler | h1. HOWTO review backport PRs |
|---|---|---|---|
| 2 | |||
| 3 | Each backport PR (or backport tracker issue) should state: |
||
| 4 | |||
| 5 | 1. what bug is fixed |
||
| 6 | 2. why this fix is the minimal way to do it |
||
| 7 | 3. why does this need to be fixed in <release> |
||
| 8 | |||
| 9 | For backport PRs opened by others, the role of the Stable Releases and Backports team members is to make sure these three questions are answered. |
||
| 10 | |||
| 11 | For backport PRs opened by members of the Stable Releases and Backports team, the team member should consider these questions and answer them in the PR or tracker issue. If the backporter does not feel comfortable answering the questions, it's better to ask someone else to do the backport. For example, one can post on the <code>#ceph-devel</code> IRC channel and ask who would be a suitable person to ask for help with the backport. |
||
| 12 | |||
| 13 | Answering these three questions in advance is important because it saves time of the leads who are involved in the code review process. |