HOWTO schedule an issue for backporting » History » Revision 4
Revision 3 (Loïc Dachary, 05/22/2015 09:14 AM) → Revision 4/14 (Loïc Dachary, 05/22/2015 09:15 AM)
h3. First stage Although this can be done by back the backporter when (s)he notices an issue should be backported, it is usually done by the original developer when (s)he realizes the fix must be backported. * Add the name of the release to the comma separated list of release in the **Backport** field of the issue (see "journal Unable to read past sequence 406":http://tracker.ceph.com/issues/6003 for instance). * Change the issue status to *Pending Backport* h3. Second stage This is not expected from the developer, it is the responsibility of the backporter. * visit the list of pending backports for the release (for instance "pending hammer backports":http://tracker.ceph.com/projects/ceph/issues?query_id=77) * each issue should have a number of *Copied from* related issues that matches the number of releases in the *backports* field * for each issue that misses at least a *Copied from*, visit the issue * *copy* the issue (link on the top right of the issue) ** change the *Tracker* to *Backport* ** change the *Status* to *New* ** empty the *Description* ** keep the *Subject* as is ** set the *Release* to the target release ** unset the *Assigned* field or set it to the person who will work on the backport. It is usually wrong to set it to the developer who fixed the issue in master. ** unselect *copying attachement* if any (this only shows if the original issues had attachements) ** unselect *Include link to original story*