HOWTO schedule an issue for backporting » History » Revision 13
Revision 12 (Loïc Dachary, 11/17/2015 07:43 PM) → Revision 13/14 (Nathan Cutler, 03/07/2017 01:17 PM)
h3. First stage
Although this can be done by 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.
"ceph-workbench":http://ceph-workbench.readthedocs.org/ <code>backport-create-issue --redmine-key $redmine_key --dry-run</code>
You can find out your Redmine API key by going to http://tracker.ceph.com/my/account (while logged in) and clicking on the "Show" link under "API access key".
h3. Backport field in the commit messages
Calling for backport by including a line like <code>Backport: firefly</code> in the commit message is discouraged because the commit message is immutable. An issue in the *Backport* tracker of the corresponding project at http://tracker.ceph.com/ should be created instead. Or, if the commit is associated with an existing issue, the *Backport* field should be updated with a comma-separated list of desired backports. Use release code names, not version numbers.