A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.
To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).
Bugzilla conventions: Difference between revisions
No edit summary |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 7: | Line 7: | ||
;'''<video>''' | ;'''<video>''' | ||
:bugs relating to <video>, <audio>, HTMLMediaElement, Controller, WebVTT, WebRTC (PeerConnection and Stream), and closely related topics. | :bugs relating to <video>, <audio>, HTMLMediaElement, Controller, WebVTT, WebRTC (PeerConnection and Stream), and closely related topics. | ||
;'''<track>''' | |||
:bugs relating to WebVTT and related topics. | |||
;'''WF2:''' | ;'''WF2:''' | ||
:bugs relating to form controls. | :bugs relating to form controls. | ||
| Line 20: | Line 22: | ||
== Severities == | == Severities == | ||
All bugs should be normal severity | All bugs should be normal severity. Bugs that need dealing with ASAP (because they are blocking implementer work) should be marked blocker. I use other severities for prioritising important or less important bugs. | ||
== Status Whiteboard == | |||
;'''reg''' | |||
:something related to the rel, meta, or other registries (and probably pending a decision on how to deal with them all) | |||
;A single letter value | |||
:part of a temporary grouping (e.g. so I can deal with related bugs together) | |||
== Components == | == Components == | ||
Latest revision as of 17:30, 2 November 2011
These are the conventions used for bugs filed in the W3C Bugzilla for specs also maintained by the WHATWG.
Subject prefixes
Some specific topics have prefixes in the bug summaries to help group the bugs.
- <video>
- bugs relating to <video>, <audio>, HTMLMediaElement, Controller, WebVTT, WebRTC (PeerConnection and Stream), and closely related topics.
- <track>
- bugs relating to WebVTT and related topics.
- WF2:
- bugs relating to form controls.
- WF3:
- feature requests relating to form controls.
- PUB:
- something relating to the spec publication process (including anolis, spec splitter, the START and END markers, etc)
Priorities
See bug priority policy according to the chairs. Initial commenters are only allowed to set priority to P3 or lower. Editors and editorial assistants can change it freely. Chairs can decide on a final priority. P1 is very urgent. P2 or P3 is for technical comments except possibly feature requests. P4 or P5 is editorial or non-technical, or feature requests.
Severities
All bugs should be normal severity. Bugs that need dealing with ASAP (because they are blocking implementer work) should be marked blocker. I use other severities for prioritising important or less important bugs.
Status Whiteboard
- reg
- something related to the rel, meta, or other registries (and probably pending a decision on how to deal with them all)
- A single letter value
- part of a temporary grouping (e.g. so I can deal with related bugs together)
Components
The bug filing system should automatically pick the right component. The components are pretty self-explanatory. WHATWG-specific issues should be moved to the "other Hixie drafts" component.
Resolutions
The boilerplate used when resolving the bug comes from: http://lists.w3.org/Archives/Public/public-html/2009Oct/0680.html
The requirements for use of different resolutions are here:
http://dev.w3.org/html5/decision-policy/decision-policy-v2.html#bug-resolutions
Helpful query links
- List of all open and deferred HTML-related bugs
- List of LATERed bugs. Some of these are commonly duped. In particular bug 7798 is TextMetrics.height which is often requested.
- List of all open bugs in specs edited by Hixie, sorted by ascending last change time
Bookmarklets
If you're helping with the bugs you may find these bookmarlets useful.