Red Hat Bugzilla – Bug 465357
Create way for Bugzilla to track release schedules internally for future use
Last modified: 2013-06-23 22:14:28 EDT
Description of problem:
Create way for Bugzilla to track release schedules internally for future use.
This will be tied to the new rh_release table which in turn is tied to the
| release_id | phase | dt_open | dt_close |
release_id = FK to rh_release
phase = ENUM(requirements,
dt_open = date phase begins
dt_close = date phase stops
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
As part of the recent Bugzilla 2.4 upgrade the Bugzilla team are cleaning up bugs opened against old versions of Bugzilla. This bug has been flagged as an old bug and will be CLOSED WONTFIX in 7 days time.
If you believe this bug is an issue in the latest Bugzilla version please comment on this bug within 7 days. Doing so will ensure this bug is not closed automatically.
Thanks, the Bugzilla team.
As noted previously, the Bugzilla Team is cleaning up a large number of outstanding issues that have bit rotted. This bug is being closed as there has been no response to that notification.
If you believe this bug is still important please reopen this bug in the NEW status and PM will consider it.