Roman Zippel a écrit :
[Skip]
Hmmm, I doubt that this work out well. It's just a feeling.
Most m68k users are using stable, I'd say, so a stable release would fit
best the needs of our users. Forcing them to use testing might be a bad
idea.
Having it be a "stable" release means handling security updates for 1.5
years or more, which can be a significant amount of work, since it has
to be in addition to the ongoing effort to maintain testing/unstable.
No doubt of that, but how how does a theoretical set of "release criteria"
automatically ensure this work is done in the future?
I wouldn't call the release criteria "theoretical" (they're even
starting to get applied), but they don't automatically ensure that the
security work is done. They should help to limit the work though.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
