Hi Release Team, I want to make sure that you're aware of what I consider HIGHLY inappropriate behavior by Chuck where he is trying to sidestep/override the Xen maintainers by filing this bug directly to the release.debian.org pseudo package. This only appeared on the Debian Xen maintainers' ML because Chuck went on a severity-dance where he *also* changed the severity of bug #994899, which _is_ assigned to the Xen package and therefor the Xen maintainers could see it. In https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994899#10 I tried to steer the efforts to getting the issue fixed in a more constructive manner. I failed at that. We've already identified a possible fix, which I can point to if so desired, but I don't think the RT should be bothered with this (dispute). It may be news to Chuck, but not the RT, but a package maintainer has the prerogative to include additional patches in the package that gets uploaded to the Debian archive. (It happens all the time) And that can introduce bugs. Shit happens. You learn from that. And then you go on fixing those bugs *in coordination with* the package maintainers. What you don't do, is try to go above/around them by addressing the RT directly. One should have at least the decency to directly To/CC the package maintainer when you do, which in 99.99+% of cases you REALLY should not do. Regards, Diederik
Attachment:
signature.asc
Description: This is a digitally signed message part.