Bug#679562: developers-reference: note that it is possible for Release Team to override urgency
Le Sun, Jul 01, 2012 at 09:33:18AM +0200, Paul Gevers a écrit :
> Index: pkgs.dbk
> ===================================================================
> --- pkgs.dbk (revision 9236)
> +++ pkgs.dbk (working copy)
> @@ -2388,7 +2388,8 @@
> the urgency is sticky, meaning that the highest urgency uploaded since the
> previous <literal>testing</literal> transition is taken into account. Those
> delays may be doubled during a freeze, or <literal>testing</literal>
> -transitions may be switched off altogether;
> +transitions may be switched off altogether. The Debian Release team can override
> +the urgency;
Dear Paul,
Than you for your patch.
I am not sure what is meant by "overriding the urgency". The Release team can
directly control the migration time for a package, but this is not exactly done
by replacing the urgency by another value, nor by ignoring it altogether. See
http://release.debian.org/britney/hints/README
Perhaps your patch would gain by being a bit more precise. Also, the urgency might
be used for other purposes than the transitions to Testing (like determining
the priority for autobuilding ?)
By thw way, is the sentence "Those delays may be doubled during a freeze" still
acccurate ? Otherwise, this bug may be the opportunity to remove it.
Have a nice Sunday,
--
Charles Plessy
Tsurumi, Kanagawa, Japan
Reply to: