On Sun, 19 May 2013 15:40:27 +0200 Jeroen Roovers <j...@gentoo.org> wrote:
> Private messages and public comments through bugzilla are so far > ignored, it seems, so let's try a venue where it's sure to cause a > flamewar instead. My apologies for the inconvenience. Since you are the BW lead, I have followed your suggestion and done so since; but as I stated last time, there's no indication for others to follow this as far I can see. Maybe there is, then please show us. > On Sat, 18 May 2013 21:08:53 +0000 > bugzilla-dae...@gentoo.org wrote: > > > DO NOT REPLY TO THIS EMAIL. Also, do not reply via email to the > > person whose email is mentioned below. To comment on this bug, > > please visit: https://bugs.gentoo.org/show_bug.cgi?id=470392 > > > > Bug ID: 470392 > > Summary: Please stabilize =dev-libs/libconfig-1.4.9-r1 > > We agreed a little while ago that bug Summaries should start with an > atom, if possible, and explain the action later. Also, robotically > filing thousands of bugs and making them say "please" every time isn't > going to endear anyone to your cause. So do something like this: > > "<cat/pkg-version> stabilisation request" > This is missing a reference URL or at least the ML thread subject; last time I asked, I didn't got either and wasn't able to find this in a reasonable amount of time. I find some irrelevant policy discussions but nothing that indicates the order in the summary. There are some developers that tend to point to history this way, they don't take into account how though it can be to search these threads if you don't use the wrong keywords to find the wrong subject. In 5 years from now, I don't think anyone is going to find "robo-stable bugs" searching for "please stabilize", "bug summary order" or any other thing along those lines. I could read the whole history, but that keeps me from contributing. > > URL: > > http://packages.gentoo.org/package/dev-libs/libconfig? arches=linux > > Is this URL useful to include, or did you just want to abuse every > last feature found in pybugz? Wouldn't maintainers already know where > to find this kind of information? Who do you think is your audience? +1 > > Severity: enhancement > > Is a stabilisation an enhancement per se? If all stabilisations are > enhancements, then why isn't Severity set to Normal instead? (What is > an enhanced severity to begin with, Mozilla?) > > > Priority: Normal > > This is where you probably wanted to set something similar to > Enhancement above, but again you probably shouldn't. Normal > stabilisation bugs are normal, not less than normal. Severity and Priority on the Gentoo Bugzilla have always been weird to me; I would love to hear from someone who is actually using either of those to sort their bugs and using them happily, because the inconsistency applied by different people is making a mess of them. The only case where I see them as useful is when people raise them to a higher priority for bugs that are really more important than the average bug, it makes them stand out in their list. We should standardize these in a way we don't have to memorize what they mean for every different type of bug, as that's the only way it is really going to make these fields make much more sense than something we tend to normalize and forget about. Why are bugs that block users from being able to use the package given a "normal" priority? > > Is it OK to stabilize =dev-libs/libconfig-1.4.9-r1 ? > > > > If so, please CC all arches which have stable keywords > > > > for older versions of this package and add STABLEREQ keyword > > > > to the bug. > > My e-mail editor is messing up the line endings here, but your > messages already include double newlines - on bugzilla web pages as > well as in the e-mail it sends, so this is your broken pybugz script > again, I reckon? That's so we can print the bug mail and write notes in between. =) > Also, your script does not set the STABLEREQ keyword. People are > having to hunt down your robo-stabilisation requests and add it > themselves. You should just do it yourself or turn your script off. Maintainer(s) and arch team member(s) blamed me for setting this. :( -- With kind regards, Tom Wijsman (TomWij) Gentoo Developer E-mail address : tom...@gentoo.org GPG Public Key : 6D34E57D GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
signature.asc
Description: PGP signature
