From: Saul Wold <sgw@linux.intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: Yocto Project Discussion <yocto@yoctoproject.org>
Subject: Re: Bugzilla Reorg Take 2
Date: Wed, 17 Nov 2010 21:29:50 -0800 [thread overview]
Message-ID: <4CE4B9CE.6080102@linux.intel.com> (raw)
In-Reply-To: <625BA99ED14B2D499DC4E29D8138F1504D31419DC1@shsmsx502.ccr.corp.intel.com>
On 11/17/2010 09:21 PM, Tian, Kevin wrote:
>> From: Saul Wold
>> Sent: Thursday, November 18, 2010 7:32 AM
>>
>>
>> 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
>> - Cross-prelink
>> - general
>> - poky integration
>> - Swabber
>> - general
>> - poky integration
>> - Pseudo
>> - general
>> - poky integration
>> - Eclipse Plugin
>> - Anjuta Plugin
>> - Yocto Image Creator (is this really standalone)?
>> - Kernel
>> - build
>> - configuration
>> - runtime
>> - BSPs
>> - by board??
>> - Test Suite
>>
>> Yocto Infrastructure
>> - Autobuilder
>> - Bugzilla
>> - Website
>>
>> Poky
>> - Build System
>> - bitbake
>> - configuration
>> - layers
>> - general
>
> is it too subtle here? Just 'build system' may be easier to understand...
>
Honestly, I am not catching your meaning here.
Sau!
> Thanks
> Kevin
>
>> - Recipes
>> - connectivity
>> - core
>> - devtools / tool chain
>> - graphics
>> - multimedia
>> - demoapps
>> - general
>> - Documentation
>> - Handbook
>> - SDK
>> - Security
>> - SDK
>> - tools
>> - general
>>
>> Comments?
>>
>>
>> --
>> Sau!
>>
>> Saul Wold
>> Yocto Component Wrangler @ Intel
>> Yocto Project / Poky Build System
>>
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
next prev parent reply other threads:[~2010-11-18 5: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
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 [this message]
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=4CE4B9CE.6080102@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=kevin.tian@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.