Thiemo Seufer wrote:
Tollef Fog Heen wrote:* Thiemo Seufer | For anyone who uses Debian as base of a commercial solution it is a| requirement. Grabing some random unstable snapshot is a non-starter. You do realise this is exactly what Ubuntu is doing? (Grab «random» snapshot; stabilise)The "stabilise" is the missing part in the proposal. Stabilization and security would need to be done outside Debian.
From the announcement: --- Architectures that are no longer being considered for stable releases are not going to be left out in the cold. The SCC infrastructure is intended as a long-term option for these other architectures, and the ftpmasters also intend to provide porter teams with the option of releasing periodic (or not-so-periodic) per-architecture snapshots of unstable. ---What that actually means is that when porters want to stabilise, they'll be able to simply stop autobuilding unstable, fix any remaining problems that are a major concern, and request a snapshot be done. That'll result in a new "snapshot-20050732/main/binary-foo" tree matching the work in unstable and a corresponding source tree; at which point CDs/DVDs can be burnt from the snapshot, and unstable development can continue. That tree will persist for a while, depending on how much archive space it takes up.
That means that porters will have to do their own security and release work, rather than relying on the primary security and release teams.
That's a serious amount of work, likely to be multiplied several times because there's no release candidate to collect it in one place.
And yes, it's a serious amount of work already, which is why the security and release teams want to stop having to do it :)
Cheers, aj