Skip to content

Commit fd5c17f

Browse files
committed
spec/issue-tracking: [Where to Track Issues]
1 parent 24181ad commit fd5c17f

1 file changed

Lines changed: 4 additions & 3 deletions

File tree

spec/issue-tracking.txt

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,11 @@
44

55
Issues are tracked in the CSS Working Group by the spec editors using one of the following mechanisms (per the editors' preference):
66

7+
* [[https://github.com/w3c/csswg-drafts/issues|GitHub issues]] (preferred)
78
* [[:spec|Wiki]] (fantasai notes from experience that if you track all issues in one page, it will eventually get [[:spec:css2.1|unweildy]], so consider a method for using sub-pages)
8-
* [[http://w3.org/Style/CSS/Tracker/|Tracker]]
9-
* [[http://www.w3.org/Bugs/Public/|Bugzilla]]
10-
* Inline in the spec itself
9+
* [[http://w3.org/Style/CSS/Tracker/|Tracker]] (historical)
10+
* [[http://www.w3.org/Bugs/Public/|Bugzilla]] (historical)
11+
* Inline in the spec itself (please avoid for non-trivial issues)
1112

1213
Each spec has a link in its header to where issues are tracked for the draft (e.g. see "Issues List:" in header of [[http://dev.w3.org/csswg/css3-ui/|CSS3-UI editor's draft]]). If all issues are tracked in the draft itself, this points to the editor's draft.
1314

0 commit comments

Comments
 (0)