Re: Backports, Stable releases, Testing, Oh my!

[Vincent Cheng <vcheng@debian.org>]

On Tue, Feb 25, 2014 at 3:33 PM, Paul Wise <pabs@debian.org> wrote:

>> What shall we do? Remove from stable-bpo? Hope an update comes around?
>> Does it make sense to revisit the rules? Does a wait until testing still
>> make sense (ok, waiting always makes sense, but beyond the 'let it
>> settle' thing)
>
> Autoremoval from backports possibly makes sense?

My concern with autoremoving packages from backports is that it would
take an extended amount of time to get the package back into backports
after the RC bug is fixed; it'd have to go through the backports NEW
queue again, whereas packages in unstable don't need to take a detour
through the NEW queue in order to re-migrate to testing. It'd be even
more annoying for folks who contribute backported packages but aren't
actually the maintainers of the package; they may well be caught by
surprise when a RC bug that they didn't know about causes their
backports to be autoremoved, especially if it was a RC bug that only
had an impact in testing/unstable, and not in a stable+backports
environment.

Regards,
Vincent