Hi, > This was downgraded to normal, without comment, by > "Adam D. Barratt" who is not a Debian developer and > is not listed in any ftpmaster documentation I can find > either in the list at http://www.debian.org/intro/organization > or http://ftp-master.debian.org/.
No, I'm not a developer. I have however being triaging ftp.d.o bugs for some time now. >In addition, I could not find out what his real email address > is so that I could ask him about it. The address in From: works perfectly. :-) (as hundreds of spammers endeavour to prove each day :() > My reason for marking it serious is that it is > preventing lilypond from making a crucial transition > into testing, and that this bug report is exactly what > Steve Langasek, the chief release manager, said > was what I should do. (I read -release). I don't remember Steve suggesting you file the bug at a release-critical severity, but apologies if I missed that. > I could understand if it was to be marked important > instead of serious, except that it is fixing a release-critical > issue for lilypond. The main reason for doing so that is that the ftp team (at least those regularly processing removals) don't use severities for that processing. In fact, as has been pointed out by Steve himself and at least one other member of the release team (on IRC, admittedly), removals from unstable can (almost) never be release-critical. The ftp-master team member who processes most of the removal bugs usually sets new removals to normal himself if he notices they're higher. As part of my triaging I do the same. However I have no desire to play bts ping-pong so I'll leave things as they are. > However, downgrading it, without comment, by someone who > is apparently not connected with Debian in any way I can > determine, does not seem entirely kosher, so I restored the > severity as I set it originally. > Adam, if you read this, please give reasons for actions, Hopefully the above is enough explanation. If not, please let me know (although I'll be away from Tuesday evening UTC until some point Thursday or Friday, so may be a little slow in replying). > and a real email address too. See above :) Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
