[Secure-testing-team] Security update for fuse

[Ulf Harnhammar]

On Wed, Jun 08, 2005 at 01:49:01PM +1000, Andrew Pollock wrote:
> I think the biggest misnomer with testing-security is its name. Think of it
> as sarge-security. This is why it was a blocker for the release - we needed
> it for after sarge became stable. So what was testing-security just got
> promoted to stable-security when we released sarge. Arguably the
> wood-security stuff should get recycled into etch-security, but I think that
> we provide oldstable security support for a bit, so we either need to go
> through the hassle of setting up etch-security now, or wait until resources
> are freed up from oldstable-security.

This testing security list was created recently, but Debian has released many
times before. How was this type of problem handled earlier? (Simultaneous
upgrades for potato and slink, for instance.)

// Ulf