HOWTO triage incoming Pending backport issues » History » Version 1
Nathan Cutler, 06/07/2015 04:33 PM
| 1 | 1 | Nathan Cutler | h3. HOWTO triage incoming Pending backport issues |
|---|---|---|---|
| 2 | |||
| 3 | Go to the appropriate "Backports (pending)" custom query: |
||
| 4 | |||
| 5 | * firefly: http://tracker.ceph.com/projects/ceph/issues?query_id=75 |
||
| 6 | * hammer: http://tracker.ceph.com/projects/ceph/issues?query_id=77 |
||
| 7 | |||
| 8 | 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. |
||
| 9 | |||
| 10 | 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: |
||
| 11 | |||
| 12 | # click on the issue number |
||
| 13 | # click on "Copy" |
||
| 14 | # change *Tracker* to "Backport" |
||
| 15 | # remove all text from the *Description* |
||
| 16 | # change *Status* to "New" |
||
| 17 | # 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) |
||
| 18 | # set *Target version* to blank unless you know exactly which version it will go into |
||
| 19 | # set *Release* to the target release |