Stefan Fritsch wrote: > Updates that fix security issues usually have urgency=high and change > faster to testing. However, you cannot trust this since new release > critical bugs might still keep the new package from entering testing. New release critical bugs need not keep a security update from testing, unless the new release with the security update itself introduced more release critical bugs than it solved. If unrelated RC bugs are filed, the release team has the power to force a security fix into testing anyway. Dependency issues blocking a security update from reaching testing remains the main blocker for security updates reaching testing and probably will continue to do so until the autobuilders fully support testing. -- see shy jo
Attachment:
signature.asc
Description: Digital signature