All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: Yocto Project Discussion <yocto@yoctoproject.org>
Subject: Re: Bugzilla Reorg Take 2
Date: Wed, 17 Nov 2010 17:29:35 -0800	[thread overview]
Message-ID: <4CE4817F.3070007@linux.intel.com> (raw)
In-Reply-To: <4CE46608.1010708@linux.intel.com>

On 11/17/2010 03:32 PM, Saul Wold wrote:
>
> Folks,
>
> After reviewing the emails from the first attempt and review bugzilla,
> there are a couple of different approaches that can be taken. It's
> important to note that bugzilla supports 3 layers, Classification,
> Product and Components, version are tracked at the Product level.
>
> Since we have 3 Layers, there are 2 possible scenarios:
>
> This is the Yocto Projects Bugzilla, so each "project" can have it's
> own classification, I am not sure that this is the best since some of
> the projects are pretty flat the extra level does not make sense.
>
> I am proposing the following top level classifications, containing the
> following projects (products/components) :
>
> Yocto Projects
...
> - Kernel
>   - build
>   - configuration
>   - runtime

Acked-by: Darren Hart <dvhart@linux.intel.com>

> - BSPs
>   - by board??

Let's start off simple - by board might not scale well. Just "BSP" would 
be my vote - Bruce might have additional thoughts.

-- 
Darren Hart
Yocto Linux Kernel


  reply	other threads:[~2010-11-18  1:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17 23:32 Bugzilla Reorg Take 2 Saul Wold
2010-11-18  1:29 ` Darren Hart [this message]
2010-11-18  5:13   ` Bruce Ashfield
2010-11-18  5:23     ` Saul Wold
2010-11-18  5:27       ` Bruce Ashfield
2010-11-18  5:21 ` Tian, Kevin
2010-11-18  5:29   ` Saul Wold
2010-11-18  5:34     ` Tian, Kevin

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=4CE4817F.3070007@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=sgw@linux.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.