Re: [Backports-queue] Processing of qemu-kvm_0.11.1+dfsg-1~bpo50+1_amd64.changes

[Al Nikolov <a.nikolov@drweb.com>]

Faidon Liambotis wrote:

> Backports are in my mind something quite similar to an NMU. The process
> is not much different: fetch a package you don't maintain, change
> something, build, test, upload and keep an eye on your inbox for bugs
> that you may have introduced.
> 
> In that sense, 30 days is just ridiculous, since the developer's
> reference suggests to wait ~10 days for NMUs not fixing RC or important
> bugs and leaves room for even less on "trivial fixes". Most backports
> are as trivial as it gets (simple rebuilds or minor build-dependency
> fixes), and I can't see the need for a delay. OTOH, I'm on the
> LowThresholdNMU list, so I may be biased here.

Moreover, since many backports are such trivial, personally, i see no point
to ask the former uploader if he or she failed to sync with the upstream
testing version on time (~10 days).

I wonder if it can be automatized: to sent a reminder to any bpo' list for a
further reference when a backported package being updated in testing? It's
current backporter can answer to it then, with 'hold still - work in
progress' (resetting the virtual timer), or with 'minor changes - wont
backport'.