This issue was discussed before in bug #5034 "Create new NSPR Product with new multiple components". We would like to revisit this issue. We want to use Bugzilla for tracking NSPR bugs. One feature we need from Bugzilla is a product-specific "target fix version" field. The closest thing that is available now is "target milestone". We could establish a mapping between milestones and NSPR versions, but that doesn't quite work. For example, suppose we establish the following mapping for NSPR: M6 <==> 3.1 M7 <==> 3.1.1 M8 <==> 3.1.2 M9 <==> 3.5 and then need to produce a 3.1.3 release. There's no milestone between M8 and M9 that we can map to version 3.1.3.

In that case, you would simply have to redefine your mapping, and do mass updates to change which bugs were assigned to which milestone. I agree the target milestone thing is not exactly what you want. But doing what you want here is not likely to happen anytime soon.

tara@tequilarista.org is the new owner of Bugzilla and Bonsai. (For details, see my posting in netscape.public.mozilla.webtools, news://news.mozilla.org/38F5D90D.F40E8C1A%40geocast.com .)

assign to me, keep this in mind during the new schema redesign

Is this bug fixed now? It looks like the set of target milestones is per-product information, and NSPR uses its own milestones.

Yes, this bug is fixed now.

OK, fixed as per reporter.

V.

moving to bugzilla product