Project

General

Profile

HOWTO schedule an issue for backporting » History » Version 7

« Previous - Version 7/14 (diff) - Next » - Current version
Nathan Cutler, 06/12/2015 08:40 AM


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 for instance).
  • Change the issue status to Pending Backport

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)
  • 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
  • verify that the new issue shows as being Copied from in the list of related issues of the original issue

Backport field in the commit messages

Calling for backport by including a line like Backport: firefly 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.