On Sun, Nov 16, 2008 at 06:02:00PM +0100, Josselin Mouette wrote: > > > > What they are not empowered to do is to decide to release with > > DFSG violations in main. > > Sorry? The release team is empowered to release, and that includes > releasing with some known RC bugs. That’s what they’ve been doing – > including with DFSG-freeness RC bugs – since I have known this project. > > The Social Contract doesn’t say anything about stable releases, nor > about the release team. The interpretation that the release team is > somehow special is your own.
Why would it have to? Knowingly violating the Social Contract is not allowed anywhere in the project, not just in stable releases. The fact that other participants did (either intentionally or unintentionally) is by no means an excuse for the Release Team to do the same. -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]