All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Darren Hart <darren.hart@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Yocto weekly bug trend charts -- WW11
Date: Mon, 19 Mar 2012 20:18:11 +0000	[thread overview]
Message-ID: <1332188291.9740.71.camel@ted> (raw)
In-Reply-To: <4F676946.6000609@intel.com>

On Mon, 2012-03-19 at 10:13 -0700, Darren Hart wrote:
> On 03/19/2012 09:18 AM, Stewart, David C wrote:
> >> From: yocto-bounces@yoctoproject.org [mailto:yocto-
> >> bounces@yoctoproject.org] On Behalf Of Xu, Jiajun
> >> Sent: Monday, March 19, 2012 8:33 AM
> 
> >> BTW, when I check the open bug data, I find that a new variable is introduced
> >> with new bugzilla for field "severity" - janitors. We do not include the bugs
> >> marked as janitors in "Yocto Weekly Open bug Trend(Severity)". My thinking
> >> is that janitors is similar with enhancement. We could treat it as
> >> enhancement(with weight value "0"), or if we think it should be included into
> >> WDD, we could set a weight value for it. How do you think of it?
> >> Fortunately, we only have 4 bugs marked as janitors, and they are all new
> >> reported last week. We could simply update the bug trend once we make the
> >> decision.
> > 
> > I suggest we make the janitor severity the same as low in the WDD calculation.
> > 
> 
> I don't know what "low" would map to. The key says:
> 
> "The weight we use for each severity: Critical:10, Major:7, Normal:5,
> Minor:3, Enhancement:0 "
> 
> In my view, Janitors should be marked the same as Enhancement, 0. If a
> bug is important enough to track and impact release, it shouldn't be a
> janitors bug, which by definition are intended to sit in a pool for
> new-comers and irregular contributors to pick up.

I did talk briefly with Dave earlier and it was hard to decide whether
these were minor or enhancement in nature. Enhancements are about adding
new functionality, bugs of whatever severity are about issues in
existing features. Janitor class issues could be in either category so
you can argue this both ways from that perspective.

Did we end up deciding to have a janitor user to assign these too in the
end or are they going to remain with various people until assigned? If
the latter, I'd hate to see the WDD being skewed against people due to
high numbers of janitor bugs so that might sway my argument.

Cheers,

Richard








  reply	other threads:[~2012-03-19 20:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19  8:49 Yocto weekly bug trend charts -- WW11 Xu, Jiajun
2012-03-19 10:26 ` Richard Purdie
2012-03-19 15:32   ` Xu, Jiajun
2012-03-19 16:18     ` Stewart, David C
2012-03-19 17:13       ` Darren Hart
2012-03-19 20:18         ` Richard Purdie [this message]
2012-03-19 20:22           ` Darren Hart
2012-03-19 21:05             ` Saul Wold
2012-03-19 17:17     ` Richard Purdie
  -- strict thread matches above, loose matches on Subject: below --
2011-03-15  3:19 Xu, Jiajun

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=1332188291.9740.71.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=darren.hart@intel.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.