Bug 222458
Summary: | bugzilla currentrelease version enforcement doesn't make sense anymore | ||
---|---|---|---|
Product: | [Community] Bugzilla | Reporter: | Ray Strode [halfline] <rstrode> |
Component: | Bugzilla General | Assignee: | PnT DevOps Devs <hss-ied-bugs> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | devel | CC: | jneedle, mcepl |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | bugzilla 3.2 | Doc Type: | Enhancement |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-12-15 17:19:33 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ray Strode [halfline]
2007-01-12 16:54:36 UTC
CURRENTRELEASE makes a lot of sense when cleaning up Bugzilla (me being a humble Desktop Bug Triager) and I am closing bugs which are WORKSFORME and apparently working for a long time. But even then it does not seem to be necessary to have *package* version number, more useful for user could be distro version (like FC6) and of course it is much more simple for me (I don't have dwelve into changelogs of the application to find when this particular was fixed). Sounds like everyone is in agreement that Bugzilla itself should no longer enforce a mandatory fixed in value. FWIW we removed the enforcement in 3.2 anyway. The fixed in field is still there so it can be still used if needed. |