On 19.06.2012 12:16, Tshepang Lekhonkhobe wrote:
On 19/06/2012 13:08, Adam D. Barratt wrote:
I realise everyone's waiting for news of the freeze (we're working
on
it...) but please bear in mind that this is not an appropriate use
of
the Urgency field:
* Urgency high to beat the freeze.
As mentioned in the last mail we sent to d-d-a (and several at
various
points before that) if you have serious concerns that important
updates
to your package won't be included in the release, the correct
approach
is to talk to us, not try and work around us. The net effect of the
above is more likely to be that the urgency will be overriden on the
britney side as if the package had been uploaded with a lower
urgency.
How would this work? Will you modify the script to look for such
cases?
No, I was referring to cases which we noticed rather than any automatic
form of detection; otoh, debian-devel-changes isn't that hard to grep.
As Martin mentioned, britney can then be told to change the assumed
urgency on a case-by-case basis when considering migration.
Regards,
Adam
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive:
http://lists.debian.org/[email protected]
