This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9317 - bug states should distinguish the true state of the bug
Summary: bug states should distinguish the true state of the bug
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: working group Decision Policy (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 9187
  Show dependency tree / graph
 
Reported: 2010-03-25 04:01 UTC by Maciej Stachowiak
Modified: 2010-03-25 04:13 UTC (History)
5 users (show)

See Also:

Attachments

Description Maciej Stachowiak 2010-03-25 04:01:49 UTC 
Larry suggested that Bugzilla should distinguish among between "EDITOR MARKED RESOLVED" and "RESOLUTION ACCEPTED" vs. "ESCALATED".


Based on a suggestion from Larry Masinter in bug 9187.
Comment 1 Maciej Stachowiak 2010-03-25 04:13:04 UTC 
I believe the three states that Larry suggested are already distinguished:

EDITOR MARKED RESOLVED --> RESOLVED or VERIFIED state; no TrackerIssue or TrackerRequest keyword
RESOLUTION ACCEPTED --> CLOSED
ESCALATED --> TrackerIssue or TrackerRequest keyword present

There is even a table of bug states explaining this.

Since the distinction is already clearly made, I am marking this bug WORKSFORME, because I believe it is already addressed by the current policy.