Skip to contentSkip to conversation

Bugzilla Reorg Take 2

DISCUSSION Saul Wold 4 participants 8 messages Nov 17, 2010 – Nov 18, 2010

lore
Share & tools
lore

Saul Wold

author
#0 lore raw

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
- Recipes
- connectivity
- core
- devtools / tool chain
- graphics
- multimedia
- demoapps
- general
- Documentation
- Handbook
- SDK
- Security
- SDK
- tools
- general

Comments?

Signature · 5 lines
    Sau!

Saul Wold
Yocto Component Wrangler @ Intel
Yocto Project / Poky Build System
Acked-by
#1 lore raw
Quoted 18 lines · Saul Wold

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

...

Quoted 4 lines

- Kernel
- build
- configuration
- runtime

Quoted 2 lines

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

Signature · 2 lines
Darren Hart
Yocto Linux Kernel
#2 lore raw
Quoted 25 lines · Darren Hart
Quoted 18 lines · Saul Wold

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

...

Quoted 4 lines

- Kernel
- build
- configuration
- runtime

Quoted 7 lines
Quoted 2 lines

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

This is the sane thing to do. One category 'bsp'. We can specify the BSP in the subject of the bug. If a bug appears across a class of BSPs or an arch, it gets bumped to kernel runtime and is dealt with there.

We've been using this scheme for about 200 supported BSPs, so it should do just fine here as well.

Cheers,

Bruce

Quoted 1 line
author
#3 lore raw
Quoted 34 lines · Bruce Ashfield
Quoted 25 lines · Darren Hart
Quoted 18 lines · Saul Wold

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

...

Quoted 4 lines

- Kernel
- build
- configuration
- runtime

Quoted 7 lines
Quoted 2 lines

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

Quoted 8 lines

This is the sane thing to do. One category 'bsp'. We can specify the BSP in the subject of the bug. If a bug appears across a class of BSPs or an arch, it gets bumped to kernel runtime and is dealt with there.

We've been using this scheme for about 200 supported BSPs, so it should do just fine here as well.

OK, so should we 'demote' bsp to component or leave it a 'product' level with 1 general component, just trying make sure we have flexibility.

Sau!

Quoted 6 lines

Cheers,

Bruce

Quoted 1 line
#4 lore raw
Quoted 40 lines · Saul Wold
Quoted 39 lines · Bruce Ashfield
Quoted 25 lines · Darren Hart
Quoted 18 lines · Saul Wold

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

...

Quoted 4 lines

- Kernel
- build
- configuration
- runtime

Quoted 7 lines
Quoted 2 lines

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

This is the sane thing to do. One category 'bsp'. We can specify the BSP in the subject of the bug. If a bug appears across a class of BSPs or an arch, it gets bumped to kernel runtime and is dealt with there.

Quoted 6 lines
Quoted 3 lines

We've been using this scheme for about 200 supported BSPs, so it should do just fine here as well.

OK, so should we 'demote' bsp to component or leave it a 'product' level with 1 general component, just trying make sure we have flexibility.

Keep the flexibility. That way if a particular BSP is maintained differently, we have the ability to assign bugs to it and keep them out of a global BSP queue.

At least that's my opinion :)

Bruce

Quoted 8 lines

Sau!

Quoted 6 lines

Cheers,

Bruce

Quoted 1 line
#5 lore raw
In reply to Saul Wold
Quoted 46 lines

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

Quoted 6 lines

Poky
- Build System
- bitbake
- configuration
- layers
- general

is it too subtle here? Just 'build system' may be easier to understand...

Thanks
Kevin

Quoted 30 lines

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

author
#6 lore raw
Quoted 46 lines · Kevin
Quoted 46 lines

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

Quoted 9 lines
Quoted 6 lines

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!

Quoted 33 lines

Thanks
Kevin

Quoted 30 lines

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

#7 lore raw
Quoted 57 lines

From: Saul Wold [mailto:[email protected]]
Sent: Thursday, November 18, 2010 1:30 PM

Quoted 53 lines · Kevin
Quoted 52 lines

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

Quoted 5 lines
Quoted 2 lines

is it too subtle here? Just 'build system' may be easier to understand...

Honestly, I am not catching your meaning here.

Sau!

Sorry, I meant that we could just have "built system" there, and no need for next level.

Thanks,
Kevin

Quoted 34 lines
Quoted 34 lines

Thanks
Kevin

Quoted 30 lines

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