From: "Xu, Jiajun" <jiajun.xu@intel.com>
To: Saul Wold <sgw@linux.intel.com>,
"'yocto@yoctoproject.org'" <yocto@yoctoproject.org>
Subject: Re: Bugzilla Changes
Date: Tue, 2 Nov 2010 00:50:06 +0800 [thread overview]
Message-ID: <D5AB6E638E5A3E4B8F4406B113A5A19A300B6ECE@shsmsx501.ccr.corp.intel.com> (raw)
In-Reply-To: <4CCBDC67.4050306@linux.intel.com>
>
> We need to review the existing Bugzilla and update the Products and
> Categories to reflect the projects correctly. Please review this
> email and make comments, suggestions for moving forward with a better
> Bugzilla categorization.
>
> Currently we have "Core OS" with the following Components:
> General
> Graphics Driver
> Kernel
> Tool Chain
> Along with "Poky" which contains:
> General
> SDK Tools
> There are also product categories for "Runtime Distribution", "Sato"
> and "SDK Plugins". Along with other infrastructure items.
>
> I would propose that we clearly define the some new products and move
> bugs as appropriate:
>
> Poky Build System - for Poky class and configuration issues User Space
> - for user space, patching and runtime failures Tool Chain - break it
> down to compiler, tools, libraries, and general Kernel - Break it down
> to Arch / Config components SDK - For all SDK related issues, have
> components for plugin, tools, ...
> Sato - as it exists today
> Runtime Distribution- Delete this, we are not a distro (no bugs now)
>
> Additionally, there is other discussion about Poky Test components for
> the standards tests such as LSB, LTP, Posix.
>
These test suites can help to find bugs from user level to kernel. It's hard to put them as components under just one product. User can decide the product and add note in bug title that the bug is for LSB or LTP.
If we want to make it easier to report bugs for such test suites, how about adding a Standard Test Suite product, which includes LSB, LTP, POSIX and Others as components.
> We will need to add Product Categories for other Yocto Projects that
> do not have bugzilla yet.
>
> Finally we need to update the Bugzilla Interface to be Yocto Project,
> changing naming as appropriate.
>
> Please take a few minutes to review this and give some feedback.
>
>
> Thanks
>
> Sau!
> Saul Wold
> Yocto Component Wrangler @ Intel
> Yocto Project / Poky Build System
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.pokylinux.org/listinfo/yocto
Best Regards,
Jiajun
next prev parent reply other threads:[~2010-11-01 16:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-30 8:50 Bugzilla Changes Saul Wold
2010-11-01 16:50 ` Xu, Jiajun [this message]
2010-11-01 19:00 ` Mark Hatle
2010-11-01 20:25 ` Saul Wold
2010-11-01 19:17 ` Darren Hart
2010-11-01 19:43 ` Mark Hatle
2010-11-01 20:13 ` Saul Wold
2010-11-01 21:40 ` Bruce Ashfield
2010-11-01 23:42 ` Darren Hart
2010-11-02 19:13 ` Bruce Ashfield
2010-11-01 19:56 ` Foster, Dawn M
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=D5AB6E638E5A3E4B8F4406B113A5A19A300B6ECE@shsmsx501.ccr.corp.intel.com \
--to=jiajun.xu@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.