On Sat, Apr 14, 2007 at 09:23:03PM -0400, Matthew Miller wrote: > On Sat, Apr 14, 2007 at 01:20:30AM +0200, Axel Thimm wrote: > > > If there's not an easy bugzilla feature to turn off new bugs for a given > > > version, > > I think all you have to do is give bugzilla the new range of versions, > > e.g. simply remove the non desired one from the config. Since the > > database backend wires in the actual text of the version into the bug > > report, it doesn't matter whether some records contain versions that > > semantically cannot be set to anymore. Maybe that was even the plan > > behind this design. > > Except how do you query for closed bugs against the version, then? Good catch! My suggestion was to short-sighted - one could split the version list for new bugs and for querying bugs, but that now sounds far worse than moving versions over to another closed product. -- Axel.Thimm at ATrpms.net
Attachment:
pgpPY3ZhKAF8y.pgp
Description: PGP signature
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
