Bugzilla – Full Text Bug Listing
| Summary: | Final status for bugzilla bugs | ||
|---|---|---|---|
| Product: | Community | Reporter: | Wim Jongman <wim.jongman> |
| Component: | Architecture Council | Assignee: | eclipse.org-architecture-council |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | david_williams, Lars.Vogel, markus.kell.r |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Wim Jongman
Actually, the problem is upstream: Bugzilla itself doesn't even describe what CLOSED is for. https://bugzilla.mozilla.org/page.cgi?id=fields.html#bug_status I've opened a bug at Mozilla. At the very least, they can perhaps provide insight as to what the intention of the status is. https://bugzilla.mozilla.org/show_bug.cgi?id=759168 (In reply to comment #0) > CLOSED -> no action in code, the issue has gone or not gone but we stop working > on it. This isn't the traditional meaning of CLOSED in bugzilla. I don't know why it is not documented in bugzilla 4, but older bugzilla versions had this help text: RESOLVED A resolution has been taken, and it is awaiting verification by QA. From here bugs are either re-opened and become REOPENED, are marked VERIFIED, or are closed for good and marked CLOSED. VERIFIED QA has looked at the bug and the resolution and agrees that the appropriate resolution has been taken. Bugs remain in this state until the product they were reported against actually ships, at which point they become CLOSED. CLOSED The bug is considered dead, the resolution is correct. Any zombie bugs who choose to walk the earth again must do so by becoming REOPENED. In Eclipse use of these states varies across projects. Some don't use CLOSED at all, others don't use VERIFIED at all... I don't think CLOSED was ever widely used in Eclipse projects. Some reporters set bugs to CLOSED manually for whatever reason. Nowadays, the CLOSED state is used more often because the "Mark as Duplicate" link now sets the status to CLOSED automatically. I'm not sure who or what caused this change. Maybe it was an experiment in bug 288133. However, I think this should should be reverted so that "Mark as Duplicate" sets the status to RESOLVED again: Set "Administration > Parameters > Bug Change Policies > duplicate_or_move_bug_status" to RESOLVED and make sure "commentonduplicate" is set to Off. I would just remove CLOSED (others may still be attached to it, though). Moving to architecture council (should have been there to begin with?), to perhaps come up with final "resolution" :) of this bug? Since the Mozilla bug Denis opened has been closed as "invalid" (That "closed" was intentionally removed from bugzilla 4). I'd say to remove it as a choice where possible, but since may still appear in "old data", document it where possible that "CLOSED was never widely used in a consistent manner at Eclipse, has been removed from Bugzilla 4, and current terminal state is VERIFIED." Or similar. Not sure how much the Architecture Council can do here to "dictate" anything ... it is up to each project to define their own workflow ... but, architecture council could come up with a "recommended workflow" for those looking for advice and guidance. In Bug 387214 Dani brought this to the PMC. Quote: --------- The Eclipse top-level project PMC discussed this and is in favor of removing the CLOSED state, assuming the correct state is set during migration (VERIFIED vs. RESOLVED) and assuming this will be done globally. --------- I close this bug therefore as duplicate, I hope this is ok. Even though this bug report is older, the other bug documents the decision by the PMC. *** This bug has been marked as a duplicate of bug 387214 *** |