HOWTO triage incoming Pending backport issues » History » Version 2
Loïc Dachary, 06/12/2015 09:17 AM
remove links to the actual requests to minimize the maintenance of the page and reference the page where they can be found
1 | 1 | Nathan Cutler | h3. HOWTO triage incoming Pending backport issues |
---|---|---|---|
2 | |||
3 | 2 | Loïc Dachary | Go to the appropriate "Backports (pending)" custom query, as shown at [[HOWTO#Overview-of-the-backports-in-progress|the top of the backport HOWTO]] |
4 | 1 | Nathan Cutler | |
5 | Scan the list. Each *Pending backport* issue should be copied to the appropriate backport tracker(s). That this has happened is indicated by the presence of lines like <code>Copied to #11653</code> in the *Related to* column. There should be one such line for each target release. |
||
6 | |||
7 | If the <code>Copied to</code> line is missing for any issue, you can make it by copying the issue to the relevant backport trackers: |
||
8 | |||
9 | # click on the issue number |
||
10 | # click on "Copy" |
||
11 | # change *Tracker* to "Backport" |
||
12 | # remove all text from the *Description* |
||
13 | # change *Status* to "New" |
||
14 | # set *Assignee* to yourself if desired, otherwise to blank (do not leave the original value - Assignee should always be a member of the Stable releases and backports team) |
||
15 | # set *Target version* to blank unless you know exactly which version it will go into |
||
16 | # set *Release* to the target release |