Ping? I am going to merge this in a few hours because Travis is broken.

@QuLogic It is more efficient to ping someone personally than just adding a message. I for instance do not receive emails unless ping directly.

@tacaswell This should probably also be backported to master

Everything not in master gets into it eventually after merging.

I'll do the merge ups tonight

We could use projects to keep track of what need to be backported into which branch.

That's what milestones are for, and backports should be done at merge time so they aren't forgotten.

There's no need for commit-specific forward porting because branches are merged forward in their entirety every once in a while.

The pattern we follow is 'old branches' (bug fix release + last releases doc branch) get merged up to master every so often (I just did 1.5.3-doc -> 2.x and then 2.x -> master). Only things going the other way need to be backported.

That's weird, but ok.

@QuLogic There are bunch of projects out there that manage just fine with one or two persons (release managers) doing backports. It is safer and less confusing.
I am fine doing backports myself, but it restricts the number of people who are able to merge certain PR to those who are comfortable enough with git to do so.