Database changes

[Joel Peshkin]

Jordi Bunster wrote:

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

There has been a lot of talk about doing this, but there have been an 
equal number of issues raised having to do with the UI, search 
capabilities, etc...

I strongly suggest you work on a very comprehensive proposal addressing 
all the details and showing the proposed schema changes and circulate it 
for comment before embarking on this.

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

We have been moving away from configuration files and favoring keeping 
this type of information in the database and administering it through 
the web interface.  As long as the existing components all wind up as 
components on migration, you should be OK.

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

You have to de-nightmare it in your proposal, probably through 
checksetup.  I am certain that a proposal posted here will get enough 
feedback so you will be able to tell if it is likely to get merged.  In 
particular, expect Gerv to be a major gatekeeper for the UI, expect me 
to be a stickler for group security, and expect bbaetz and myk to be 
major gatekeepers on system performance.

-Joel