Bugzilla Changes


Saul Wold <sgw@...>
 

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.

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


Xu, Jiajun <jiajun.xu@...>
 


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


Mark Hatle <mark.hatle@...>
 

On 10/30/10 3:50 AM, Saul Wold wrote:

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)
My proposal -- similar bug slightly different:

Poky Build System
Bitbake
Documentation
General

Poky Distribution
Runtime Distribution -- Poky embedded linux distribution
Documentation
Security
Toolchain
SDK
Test Suite

Yocto Infrastructure
AutoBuilder
Bugzilla
Website

Anjuta Plug-in
???

Eclipse Plug-in
???

Cross-Prelink

Pseudo

SDK Generator

Swabber


... specifically we need a major category for each of the projects in Yocto, right now the bugzilla is very specific to Poky and I think that needs to be updated now that things are public.

Additionally, there is other discussion about Poky Test components for
the standards tests such as LSB, LTP, Posix.
My suggestion is that is part of the run-time distribution. If someone chooses to not use the Poky run-time, then the tests likely won't be useful on their own.

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


Darren Hart <dvhart@...>
 

On 10/30/2010 01:50 AM, Saul Wold wrote:

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
The divide between User Space and Tool Chain is a bit vague. For instance, I would generally expect to see glibc under User Space, but your description seems to place it under Tool Chain.

and general Kernel - Break it down to Arch / Config components
Please keep the kernel separate from the Tool Chain, something along the lines of:

Kernel
- Core
- Drivers
- Tooling (Trace, Debug, Perf)

Thanks,

--
Darren

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.

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

--
Darren Hart
Embedded Linux Kernel


Mark Hatle <mark.hatle@...>
 

On 11/1/10 2:17 PM, Darren Hart wrote:
On 10/30/2010 01:50 AM, Saul Wold wrote:

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
The divide between User Space and Tool Chain is a bit vague. For
instance, I would generally expect to see glibc under User Space, but
your description seems to place it under Tool Chain.
I think this is where the Bugzilla description needs to be verbose.

Toolchain for me includes: userspace kernel headers (but not the kernel), binutils, gcc, "the libc" (uclibc, glibc, eglibc), and gdb.

> and general Kernel - Break it down to Arch / Config components

Please keep the kernel separate from the Tool Chain, something along the
lines of:

Kernel
- Core
- Drivers
- Tooling (Trace, Debug, Perf)
Yes, I agree. the kernel needs to be treated as a separate project as it is an external item to Poky -- but part of the overall Yocto Project.

--Mark

Thanks,

--
Darren

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.

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


Foster, Dawn M <dawn.m.foster@...>
 

On Oct 30, 2010, at 1:50 AM, Saul Wold wrote:


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.
We'll also want to update this document after we make these changes:
https://wiki.yoctoproject.org/wiki/Bugzilla_Configuration_and_Bug_Tracking

We might want to streamline that doc a bit to better summarize what
someone needs to know to file a bug to get people started before
diving into all of the details.

Dawn


Saul Wold <sgw@...>
 

On 11/01/2010 12:17 PM, Darren Hart wrote:
On 10/30/2010 01:50 AM, Saul Wold wrote:

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
The divide between User Space and Tool Chain is a bit vague. For
instance, I would generally expect to see glibc under User Space, but
your description seems to place it under Tool Chain.
Good point. (See my reply to Mark's email)

> and general Kernel - Break it down to Arch / Config components

Please keep the kernel separate from the Tool Chain, something along the
lines of:

Kernel
- Core
- Drivers
- Tooling (Trace, Debug, Perf)
I think my lines might have run together! It was meant to be separate, and this looks like a good break down.

Sau!

Thanks,

--
Darren

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.

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


Saul Wold <sgw@...>
 

On 11/01/2010 12:00 PM, Mark Hatle wrote:
On 10/30/10 3:50 AM, Saul Wold wrote:

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)
My proposal -- similar bug slightly different:

Poky Build System
Bitbake
Documentation
General
Add Configurations - for the config/site data

Poky Distribution
Runtime Distribution -- Poky embedded linux distribution
Remember this is not a Distribution, I think Yocto (Poky?) Meta-Data / Recipes and then the following components

Documentation
Security
Toolchain
SDK
Test Suite
Add:
User Space Recipes (this could be further broken down, if needed)
Toolchain Recipes (instead of Toolchain)
General


Yocto Infrastructure
AutoBuilder
Bugzilla
Website

Anjuta Plug-in
???

Eclipse Plug-in
???

Cross-Prelink

Pseudo

SDK Generator

Swabber
Add the Kernel Product
- Core
- Drivers
- Tooling (Trace, Debug, Perf)



... specifically we need a major category for each of the projects in
Yocto, right now the bugzilla is very specific to Poky and I think that
needs to be updated now that things are public.

Additionally, there is other discussion about Poky Test components for
the standards tests such as LSB, LTP, Posix.
My suggestion is that is part of the run-time distribution. If someone
chooses to not use the Poky run-time, then the tests likely won't be
useful on their own.

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
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.pokylinux.org/listinfo/yocto


Bruce Ashfield <bruce.ashfield@...>
 

On 10-11-01 4:13 PM, Saul Wold wrote:
On 11/01/2010 12:17 PM, Darren Hart wrote:
On 10/30/2010 01:50 AM, Saul Wold wrote:

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
The divide between User Space and Tool Chain is a bit vague. For
instance, I would generally expect to see glibc under User Space, but
your description seems to place it under Tool Chain.
Good point. (See my reply to Mark's email)

> and general Kernel - Break it down to Arch / Config components

Please keep the kernel separate from the Tool Chain, something along the
lines of:

Kernel
- Core
- Drivers
- Tooling (Trace, Debug, Perf)
I think my lines might have run together! It was meant to be separate,
and this looks like a good break down.
This is too much separation, having over categorization
of the kernel defects at this point is overkill. I'd
suggest three categories:

- kernel build (which often transitions to
straight up build-system after triage).
- kernel configuration
- kernel runtime

Let's keep it simple.

Bruce


Sau!

Thanks,

--
Darren

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.

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


Darren Hart <dvhart@...>
 

On 11/01/2010 02:40 PM, Bruce Ashfield wrote:
On 10-11-01 4:13 PM, Saul Wold wrote:
On 11/01/2010 12:17 PM, Darren Hart wrote:
On 10/30/2010 01:50 AM, Saul Wold wrote:

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
The divide between User Space and Tool Chain is a bit vague. For
instance, I would generally expect to see glibc under User Space, but
your description seems to place it under Tool Chain.
Good point. (See my reply to Mark's email)

and general Kernel - Break it down to Arch / Config components
Please keep the kernel separate from the Tool Chain, something along the
lines of:

Kernel
- Core
- Drivers
- Tooling (Trace, Debug, Perf)
I think my lines might have run together! It was meant to be separate,
and this looks like a good break down.
This is too much separation, having over categorization
of the kernel defects at this point is overkill.
Agree in principle.

I'd suggest three categories:

- kernel build (which often transitions to
straight up build-system after triage).
- kernel configuration
- kernel runtime
Let me confirm:

- kernel runtime (this includes all errors, panics, BUGs, etc. from the
three categories I listed above - no objection).

It's still 3 categories, but separate by type of bug instead of area of bug. It's still fine with me. My biggest concern was keeping the kernel separate, and it is in either form. I'll happily defer to Bruce with respect to an efficient set of kernel bug categories for an embedded "not-a-distribution".

Let's keep it simple.
Agreed.

--
Darren Hart
Embedded Linux Kernel


Bruce Ashfield <bruce.ashfield@...>
 

On 10-11-01 07:42 PM, Darren Hart wrote:
On 11/01/2010 02:40 PM, Bruce Ashfield wrote:
On 10-11-01 4:13 PM, Saul Wold wrote:
On 11/01/2010 12:17 PM, Darren Hart wrote:
On 10/30/2010 01:50 AM, Saul Wold wrote:

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
The divide between User Space and Tool Chain is a bit vague. For
instance, I would generally expect to see glibc under User Space, but
your description seems to place it under Tool Chain.
Good point. (See my reply to Mark's email)

and general Kernel - Break it down to Arch / Config components
Please keep the kernel separate from the Tool Chain, something along the
lines of:

Kernel
- Core
- Drivers
- Tooling (Trace, Debug, Perf)
I think my lines might have run together! It was meant to be separate,
and this looks like a good break down.
This is too much separation, having over categorization
of the kernel defects at this point is overkill.
Agree in principle.

I'd suggest three categories:

- kernel build (which often transitions to
straight up build-system after triage).
- kernel configuration
- kernel runtime
Let me confirm:

- kernel runtime (this includes all errors, panics, BUGs, etc. from the
three categories I listed above - no objection).
It does. What we can also do, is split it between
'kernel' and 'BSP'. I've been triaging bugs like this
for 6 years now, and typically it is very hard for
the submitters to categorize properly. But typically
they do know if it is particular to a board (BSP) or
everywhere (kernel). The BSP would also cover the drivers
category that you had listed above .. since often, drivers
are exercised by one (or few) boards and those are the
ones that have problems.


It's still 3 categories, but separate by type of bug instead of area of
bug. It's still fine with me. My biggest concern was keeping the kernel
separate, and it is in either form. I'll happily defer to Bruce with
respect to an efficient set of kernel bug categories for an embedded
"not-a-distribution".
Agreed. We are aligned here. We'll adjust these as we
go forward to whatever makes sense.

Bruce


Let's keep it simple.
Agreed.