New documentation for updates to stable releases

[Matt Zimmerman]

On Thu, Sep 21, 2006 at 08:06:29PM +0100, m c wrote:
> Will there be any changes to the security update process?

Possibly, but the process will not be the same as for non-security updates
due to requirements for confidentiality and the urgency of some security
fixes.

> A (less extensive) X borkage was caused by a recent security update, and
> although I'm sure the same problem wont happen again it shows security
> updates can be equally as damaging. Obviously delaying security updates is
> a much trickier proposition, but perhaps some sort of repository could be
> set up for people willing to test security updates quickly. Would any
> other the other steps implemented for stable release process be suitable?

The causes and circumstances of that event were quite different, and require
a separate response, which is already in progress.  The security update
process was already formally documented, and I linked to it from
StableReleaseUpdates for reference.

-- 
 - mdz