CI merger order change - backports remove

[Harald Sitter]

On Fri, Oct 9, 2015 at 9:29 AM, Scarlett Clark
<scarlett.gately.clark at gmail.com> wrote:
> Sorry did I do something wrong?

No, I did. I have no clue why backports were being merged forward into
CI branches or why I added that feature, and now those merges keep CI
busy when I am supposed to roll an ISO :'<

They also have the more important side ffects that debian/control
adjustments for vivid get into CI, get reverted, get into wily, get
into vivid, get revert-reverted (to restore backport condition), get
into CI...
Point being that they form a merge cycle of perpetual regression since
a backport doesnt have to have the same packaging as a build for
$latest so merging them into CI for latest and as a result eventually
into latest (i.e. wily_archive) makes no sense.

HS