| 2012-12-10 10:35:49 |
Iain Lane |
description |
Currently you get
"No-change backport to Release
--- <BACKPORTER>"
Which, especially when there are problems like FTBFS, makes it look like the backporter is responsible for the upload. This means that the backporter gets hassle for problems which they should really on the hook to fix.
We should either make the upload sponsored for the requesting user or add a note into the automatic changelog that the backport is on behalf of whoever. I don't know which is better; will discuss with my fellow backporters. |
Currently you get
"No-change backport to Release
-- <BACKPORTER>"
Which, especially when there are problems like FTBFS, makes it look like the backporter is responsible for the upload. This means that the backporter gets hassle for problems which they should really on the hook to fix.
We should either make the upload sponsored for the requesting user or add a note into the automatic changelog that the backport is on behalf of whoever. I don't know which is better; will discuss with my fellow backporters. |
|
