multiple instance of bugzilla

[Joel Peshkin]

Boris Baldassari wrote:

>hi;
>
>  
>
>>We've already frozen for 2.18.  Based on current progress at getting
>>past the freeze, it'll likely be about a month or a little more before
>>it's actually released, but it's coming soon.
>>    
>>
>it may be too long. hum. i could work on cvs and upgrade when 2.18 will
>come out. ok, thanks.
>
>  
>
>>You'll need to explain a little more of what you have in mind before I
>>can give a really good answer, but it's usually more headache than it's
>>    
>>
>it's not an user problem. we have several types of record (eg. cr and pr),
>each with a specific lifecycle. the point is that they all have to
>interact: a cr record may generate (dependency) a pr record, and we need
>to track them up and down.
>since only one lifecycle can be used with an instance of bugzilla (or may
>i misunderstood something?), i thought about running several instances of
>bugzilla, each with a specific (customized) lifecycle, and allow them to
>send updates for dependencies. in such a system, dependency graph would
>typically span accross several database and/or bugzilla instances.
>
>  
>
Nothing you have said would be helped by running multiple bugzilla 
instances.  Running multiple instances is something I suggest you treat 
as a last resort.  Instead of running multiple bugzillas, you can use a 
distinct product for each type of record and even customize the 
templates to change terminology on a per-product basis.

If there is something that you think can be done in multiple instances 
but not in a single instance, please mention it here.  I do not think 
such a thing exists.