Luk Claes <[EMAIL PROTECTED]> writes: > it's not the release team that is violating a foundation document. > It's Debian as a whole and it's happening now, not when we release > or not.
This is an important distinction, thank you. > The only thing we did as a release team is to make clear that we > don't want to delay the release if these bugs won't get fixed. Surely the requirement is not to *ignore* a serious bug, but to *remove* the offending package unless the bug is resolved? Yes, I understand we're talking about, in some cases, kernel packages that have these bugs. What I don't see is why these serious bugs, that (as you point out) violate the Debian project's foundation documents, can be ignored for the sake of releasing on a particular date. -- \ “I doubt, therefore I might be.” —anonymous | `\ | _o__) | Ben Finney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
