How To Request Backport

Principle

Backport is requesting branch maintainers to merge trunk's commits.
Generally only bugfixes are allowed to backport.

Overview

There's two way to request backport.
Backport ticket and backport custom field.

Backport ticket

Create ticket to requst backport on a backport tracker.

Where

NOTE: only backport ticket is available on those projects. Don't report bugs there!

Ticket

Simple backport request

  • Subject: Backport rXXXXX
  • Description: please backport!

If the commit log is enough described and you expect the maintainer accept the backport, a request can be simple.
If there's related ticket, you should add it.

Multiple backport

  • Subject: Backport rXXXXX,rXXXXX,rXXXXX-rXXXXX
  • Description: please backport!

If some commits are atomic (main commit and fix typo of it), you can request multiple commits.

Nontrivial backport

  • Subject: Backport rXXXXX
  • Description: The ticket fixes blah blah blah. I'm suffered from the bug. So backport please!

If the commit log is not enough, you need to describe why the backport is required.

Backport custom field

If you are expert CRuby developer, you can use Backport custom field.
The format of the field is /^([1-9]\.[0-9](\.[0-9])?: (UNKNOWN|REQUIRED|DONE|DONTNEED)(, [1-9]\.[0-9](\.[0-9])?: (UNKNOWN|REQUIRED|DONE|DONTNEED))*)?$/.
This is useful when you know a ticket affect a released ruby, and note it on the ticket in machine readable format.

The revisions to backport should be associated with the ticket.
If some of them are not, you should associate them on https://bugs.ruby-lang.org/projects/ruby-trunk/repository/revisions/<revision>.

If you fill the filed and the ticket is closed, a branch maintainer will backport related commits.

NOTE: Don't assign reopen, move, and assign it to branch maintainer the ticket.
They search tickets with a query whose backport field is REQUIRED and whose status is closed.