HOWTO triage incoming Pending backport issues » History » Revision 3
Revision 2 (Loïc Dachary, 06/12/2015 09:17 AM) → Revision 3/6 (Loïc Dachary, 06/12/2015 09:20 AM)
h3. HOWTO triage incoming Pending backport issues Go to the appropriate "Backports (pending)" custom query, as shown at [[HOWTO#Overview-of-the-backports-in-progress|the top of the backport HOWTO]] Follow Scan the steps list. Each *Pending backport* issue should be copied to the appropriate backport tracker(s). That this has happened is indicated by the presence of [[HOWTO_schedule_an_issue_for_backporting#Second-stage|the second stage of scheduling an issue lines like <code>Copied to #11653</code> in the *Related to* column. There should be one such line for backporting]] each target release. 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: # click on the issue number # click on "Copy" # change *Tracker* to "Backport" # remove all text from the *Description* # change *Status* to "New" # 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) # set *Target version* to blank unless you know exactly which version it will go into # set *Release* to the target release