public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jeroen Roovers <jer@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] robo-stable bugs
Date: Sun, 19 May 2013 15:40:27 +0200	[thread overview]
Message-ID: <20130519154027.37b6cdf4@marga.jer-c2.orkz.net> (raw)
In-Reply-To: <bug-470392-23709@http.bugs.gentoo.org/>

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.

On Sat, 18 May 2013 21:08:53 +0000
bugzilla-daemon@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"

>                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?

>                 OS: Linux
>             Status: CONFIRMED
>           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.

> 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?

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.


      jer


       reply	other threads:[~2013-05-19 13:40 UTC|newest]

Thread overview: 82+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-470392-23709@http.bugs.gentoo.org/>
2013-05-19 13:40 ` Jeroen Roovers [this message]
2013-05-19 14:35   ` [gentoo-dev] Re: robo-stable bugs Michael Palimaka
2013-05-19 15:51   ` [gentoo-dev] " Dirkjan Ochtman
2013-05-19 15:58   ` Markos Chandras
2013-05-19 20:22   ` Andreas K. Huettel
2013-05-20  0:00   ` "Paweł Hajdan, Jr."
2013-05-20 12:10     ` Gilles Dartiguelongue
2013-05-20 16:58       ` "Paweł Hajdan, Jr."
2013-07-27 19:29         ` "Paweł Hajdan, Jr."
2013-07-27 20:16           ` Andreas K. Huettel
2013-05-21 12:21     ` Thomas Sachau
2013-05-21 12:35       ` Chí-Thanh Christopher Nguyễn
2013-05-21 13:32         ` Thomas Sachau
2013-05-22 14:44           ` Jeroen Roovers
2013-05-21 13:20       ` Markos Chandras
2013-05-21 13:38         ` Thomas Sachau
2013-05-21 18:32           ` "Paweł Hajdan, Jr."
2013-05-21 19:51             ` Markos Chandras
2013-05-21 20:17               ` Alexis Ballier
2013-05-21 20:46                 ` "Paweł Hajdan, Jr."
2013-05-21 21:37                   ` Andreas K. Huettel
2013-05-21 22:25                   ` Alexis Ballier
2013-05-22  0:50                 ` [gentoo-dev] " Ryan Hill
2013-05-21 23:28             ` [gentoo-dev] " Thomas Sachau
2013-05-21 21:38           ` Andreas K. Huettel
2013-05-22  9:22             ` vivo75
2013-05-22  9:43               ` [gentoo-dev] " Michael Palimaka
2013-05-22 10:07                 ` vivo75
2013-05-22 10:12                   ` Michael Palimaka
2013-05-22 10:41                     ` Thomas Sachau
2013-05-22 11:06                       ` Michael Palimaka
2013-05-22 11:16                         ` vivo75
2013-05-22 13:03                           ` Ian Stakenvicius
2013-05-22 14:51                             ` Jeroen Roovers
2013-05-22 15:08                               ` Ian Stakenvicius
2013-05-22 13:02                   ` Ian Stakenvicius
2013-05-22 13:21               ` [gentoo-dev] " Rich Freeman
2013-05-21 21:22         ` Rick "Zero_Chaos" Farina
2013-05-21 23:43           ` Thomas Sachau
2013-05-21 23:51             ` Andreas K. Huettel
2013-05-22  3:46             ` Rick "Zero_Chaos" Farina
2013-05-22 13:11               ` Ian Stakenvicius
2013-05-22 23:03                 ` Rick "Zero_Chaos" Farina
2013-05-23 12:57                   ` Ian Stakenvicius
2013-05-23 18:11                     ` [gentoo-dev] robo-stable bugs, the flipside Ian Stakenvicius
2013-05-23 18:40                       ` Markos Chandras
2013-05-23 18:49                         ` Ian Stakenvicius
2013-05-23 19:29                           ` Rich Freeman
2013-05-24 13:04                             ` Ian Stakenvicius
2013-05-23 20:14                           ` Markos Chandras
2013-05-24 13:03                             ` Ian Stakenvicius
2013-05-22 12:53             ` [gentoo-dev] robo-stable bugs Ian Stakenvicius
2013-05-22 12:55               ` Michael Mol
2013-05-22 15:00               ` Jeroen Roovers
2013-05-22 15:14                 ` Michael Mol
2013-05-22 15:22                   ` Ian Stakenvicius
2013-05-20 15:29   ` Tom Wijsman
2013-05-20 17:15     ` Rich Freeman
2013-05-20 18:21       ` Tom Wijsman
2013-05-21  0:46       ` [gentoo-dev] " Duncan
2013-05-22 15:21         ` Jeroen Roovers
2013-05-23  6:22           ` Duncan
2013-05-20 18:00     ` [gentoo-dev] " Robin H. Johnson
2013-05-20 18:29       ` Tom Wijsman
2013-05-29  9:21         ` Michael Weber
2013-05-22 15:03     ` Jeroen Roovers
2013-05-22 15:27       ` Tom Wijsman
2013-05-22  0:57   ` [gentoo-dev] " Ryan Hill
2013-05-22  8:58     ` Tom Wijsman
2013-05-22  9:07       ` Ulrich Mueller
2013-05-22 11:00         ` Tom Wijsman
2013-05-22 11:07           ` Michael Palimaka
2013-05-22 12:02             ` Tom Wijsman
2013-05-24  5:20           ` Ryan Hill
2013-05-24  5:26             ` Tom Wijsman
2013-05-22  9:18       ` Michael Palimaka
2013-05-22 14:56         ` Tom Wijsman
2013-05-22 15:45         ` Jeroen Roovers
2013-05-24  5:40       ` Ryan Hill
2013-05-24  5:58         ` Tom Wijsman
2013-05-27 10:54         ` Jeroen Roovers
2013-05-22 15:36     ` Jeroen Roovers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130519154027.37b6cdf4@marga.jer-c2.orkz.net \
    --to=jer@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox