Red Hat Bugzilla – Bug 137658
Break up the Fedora product into separate major versions similar to RHEL
Last modified: 2015-01-04 17:11:20 EST
Earlier versions of a product reach end of life, and new bugs are just going to
go to /dev/null. As an example, Fedora Core 1. Bugzilla can only close complete
products (ie, 'Fedora Core'), and not specific subversions of that product.
Steps to Reproduce:
Red Hat's current Bugzilla version is 2.18. I am moving all older open bugs to
this version. Any bugs against the older versions will need to be verified that
they are still bugs. This will help me also to sort them better.
Changing this to RFE to break the Fedora product into separate versions similar to how RHEL was done.
If we move Fedora 'versions' to separate 'products'... is it possible to search bugs across several 'products'?
(In reply to comment #3)
> If we move Fedora 'versions' to separate 'products'... is it possible to search
> bugs across several 'products'?
Yes you would just select multiple ones in query select box for product in query.cgi, similar to RHEL.
Red Hat Bugzilla is now using version 3.4 of the Bugzilla codebase and
therefore this feature will need to be implemented against the new release.
Updating bug version to 3.2.
Red Hat has now upgraded to Bugzilla 3.6 and this bug will now be reassigned to that version. It would be helpful to the Bugzilla Development Team if this bug is verified to still be an issue with the latest version. If it is no longer an issue, then feel free to close, otherwise please comment that it is still a problem and we will try to address the issue as soon as we can.
Bugzilla Development Team
It seems like we have a pretty good process going now. Dave do you still see the need for this RFE? My vote is "things are good enough" and close this bug.
I think the original thing that annoyed me was that it was still possible for users to file bugs past EOL. With a closed 'product', that isn't possible afaik.
That said, it isn't a huge issue any more (maybe because users have gotten their heads around our EOL policies better), so I don't really care if this gets closed or not.
Thanks DaveJ. Will close.