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 9313 - Use some state other than CLOSED for issues that are closed without prejudice, for lack of action by a deadline
Summary: Use some state other than CLOSED for issues that are closed without prejudice...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: working group Decision Policy (show other bugs)
Version: unspecified
Hardware: All 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 03:54 UTC by Maciej Stachowiak
Modified: 2010-03-25 04:09 UTC (History)
4 users (show)

See Also:

Attachments

Description Maciej Stachowiak 2010-03-25 03:54:45 UTC 
Use some state other than CLOSED for issues that are closed without prejudice, for lack of action by a deadline. One specific suggestion is to add a new TIMEDOUT state for issues.
Comment 1 Maciej Stachowiak 2010-03-25 03:56:02 UTC 
Based on a suggestion from Larry Masinter in bug 9187.
Comment 2 Maciej Stachowiak 2010-03-25 04:06:39 UTC 
I tested, and marking an issue POSTPONED makes it distinct from CLOSED issues but it still does not show up in lists of open/unresolved issues such as the product list.

I propose that issues which time out should be marked POSTPONED instead of CLOSED in the issue tracker. I will edit the v2 policy draft per this concept. Larry, I hope that is sufficiently close to TIMEDOUT. I am told that it is difficult to get new states added to the issue tracker.
Comment 3 Maciej Stachowiak 2010-03-25 04:09:51 UTC 
I made the change to POSTPONED in http://dev.w3.org/cvsweb/html5/decision-policy/decision-policy-v2.html.diff?r1=1.4&r2=1.5&f=h