Skip to contentSkip to conversation

Bugzilla Changes

DISCUSSION Saul Wold 6 participants 11 messages Oct 30, 2010 – Nov 2, 2010

lore
Share & tools
lore

Saul Wold

author
#0 lore raw

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

#1 lore raw
Quoted 28 lines

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)

Quoted 3 lines

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.

Quoted 16 lines

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

Quoted 4 lines

_______________________________________________
yocto mailing list
[email protected]
https://lists.pokylinux.org/listinfo/yocto

Best Regards,
Jiajun

#2 lore raw
In reply to Saul Wold
Quoted 22 lines · Saul Wold

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:

Quoted 7 lines

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.

Quoted 2 lines

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.

Quoted 21 lines

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
[email protected]
https://lists.pokylinux.org/listinfo/yocto

author
#3 lore raw
Quoted 31 lines · Mark Hatle
Quoted 22 lines · Saul Wold

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:

Quoted 7 lines

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)

Quoted 7 lines

My proposal -- similar bug slightly different:

Poky Build System
Bitbake
Documentation
General

Add Configurations - for the config/site data

Quoted 2 lines

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

Quoted 5 lines

Documentation
Security
Toolchain
SDK
Test Suite

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

Quoted 12 lines

Yocto Infrastructure
AutoBuilder
Bugzilla
Website

Anjuta Plug-in
???

Eclipse Plug-in
???

Quoted 8 lines

Cross-Prelink

Pseudo

SDK Generator

Swabber

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

Quoted 38 lines

... 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.

Quoted 2 lines

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.

Quoted 13 lines

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!

Quoted 8 lines

Saul Wold
Yocto Component Wrangler @ Intel
Yocto Project / Poky Build System

_______________________________________________
yocto mailing list
[email protected]
https://lists.pokylinux.org/listinfo/yocto

_______________________________________________
yocto mailing list
[email protected]
https://lists.pokylinux.org/listinfo/yocto

#4 lore raw
In reply to Saul Wold
Quoted 19 lines · Saul Wold

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.

Quoted 6 lines

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.

Quoted 1 line

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

Quoted 28 lines

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
[email protected]
https://lists.pokylinux.org/listinfo/yocto

Signature · 2 lines
Darren Hart
Embedded Linux Kernel
#5 lore raw
Quoted 23 lines · Darren Hart
Quoted 22 lines · Saul Wold

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:

Quoted 7 lines
Quoted 3 lines

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.

Quoted 9 lines
Quoted 1 line

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

Quoted 35 lines

Thanks,

--
Darren

Quoted 28 lines

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
[email protected]
https://lists.pokylinux.org/listinfo/yocto

author
#6 lore raw
In reply to Darren Hart
Quoted 23 lines · Darren Hart
Quoted 22 lines · Saul Wold

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:

Quoted 8 lines
Quoted 3 lines

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)

Quoted 10 lines
Quoted 1 line

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!

Quoted 35 lines

Thanks,

--
Darren

Quoted 28 lines

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
[email protected]
https://lists.pokylinux.org/listinfo/yocto

#7 lore raw
Quoted 39 lines · Saul Wold
Quoted 23 lines · Darren Hart
Quoted 22 lines · Saul Wold

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:

Quoted 8 lines
Quoted 3 lines

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)

Quoted 5 lines
Quoted 1 line

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

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

Quoted 7 lines
Quoted 5 lines

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

Quoted 38 lines

Sau!

Quoted 35 lines

Thanks,

--
Darren

Quoted 28 lines

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
[email protected]
https://lists.pokylinux.org/listinfo/yocto

#8 lore raw
Quoted 47 lines · Bruce Ashfield
Quoted 46 lines · Saul Wold
Quoted 25 lines · Darren Hart
Quoted 24 lines · Saul Wold

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:

Quoted 8 lines
Quoted 3 lines

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)

Quoted 10 lines
Quoted 1 line

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)

Quoted 5 lines
Quoted 2 lines

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.

Quoted 6 lines

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".

Quoted 1 line

Let's keep it simple.

Agreed.

Signature · 2 lines
Darren Hart
Embedded Linux Kernel
#9 lore raw
Quoted 63 lines · Darren Hart
Quoted 47 lines · Bruce Ashfield
Quoted 46 lines · Saul Wold
Quoted 25 lines · Darren Hart
Quoted 24 lines · Saul Wold

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:

Quoted 8 lines
Quoted 3 lines

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)

Quoted 10 lines
Quoted 1 line

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)

Quoted 5 lines
Quoted 2 lines

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.

Quoted 6 lines

I'd suggest three categories:

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

Quoted 4 lines

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.

Quoted 6 lines

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

Quoted 5 lines
Quoted 2 lines

Let's keep it simple.

Agreed.

#10 lore raw
In reply to Saul Wold
Quoted 6 lines · Saul Wold

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