Database changes

Jordi Bunster bunsterj at convergentdev.com
Tue May 20 15:18:56 UTC 2003


Hello Folks

I'm planning to introduce some big changes on bugzilla's internal logic and 
database. Here at my shop, we have much more modularity than just the two 
level (product, component) approach. What we want to do is, just have bug 
"targets", which can nest. Each one would have a unique ID, and a parent 
reference, and you can assign bugs to any of them, not just to the lowest 
level one.

It is also my intention to have a configuration file, where you can specify 
the way a target is called on the *webpages*, not internally, depending on 
its nesting depth. For example, level one would be called product, level 
two component, and three and on sub-component, so as to avoid breakage with 
existing bugzilla installations.

Knowing that this would make upgrading bugzilla here a nightmare, my 
question goes: Would the bugzilla team be willing to accept this changes, 
providing that the code is clean, follows the guidelines, and I add code to 
checksetup.pl so that it automagically migrates everything?

I'm also open to suggestions regarding the approach, if that means 
increasing the chances of the code being merged.

 -- Jordi




More information about the developers mailing list