On Sun, Jun 19, 2005 at 10:16:34PM +0200, Josselin Mouette wrote: > > There is a simple reason for discussing that topic in the release team > > meeting: Our current RC policy makes any violation against the current > > python policy an RC bug. At this meeting, we discussed what needs to be > > changed in our RC policy list for etch in the opinion of the release > > team, and the python policy is one place where a change would be nice in > > the release teams view. It is of course the right of the python team to > > disagree with the release team; it is not the task of the release team > > to decide the python policy, but please understand that we wanted to go > > through all issues in our release policy. (Please remember that there > > are also other similar issues like the one that we want a newer LSB - > > but that needs also coordination.) > If the release team decides something, then says "we want things like > this", you're putting people in front of a fait accompli. Even if people > disagree with you, you get what the release team decided in the end, so > that the release policy is matched. So you think that the release team doesn't consider the input of other people in Debian, and that the way to make us listen to you is to be a prat about it? Wrong on both counts... -- Steve Langasek postmodern programmer
Attachment:
signature.asc
Description: Digital signature