- From: <bugzilla@jessica.w3.org>
- Date: Wed, 08 Feb 2012 01:02:47 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15630 Sam Ruby <rubys@intertwingly.net> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|rubys@intertwingly.net |ian@hixie.ch --- Comment #3 from Sam Ruby <rubys@intertwingly.net> 2012-02-08 01:02:44 UTC --- (In reply to comment #2) > The original bug isn't addressed by the given decision. The relevant portion of the decision: Note that the change requested is to keep the spec updated with respect to the statuses of the relevant documents per RFC 2026. In the time since that Change Proposal has been written, one such status has changed, and a bug report was opened to reflect that change: https://www.w3.org/Bugs/Public/show_bug.cgi?id=15630 The editor is strongly encouraged to process that bug and any others like it concurrently with the execution of this decision. > Reassigning to chairs for clarification. Reassigning back with the above clarification. Just so it is clear: the decision is to follow RFC 2026. The original Change Proposal reflected the state of the relevant specs at the time it was written. At least one spec changed state, and a separate bug report was opened on that change, and that bug was referenced in the decision. You are encouraged to process the Change Request and this bug concurrently. If for any reason you do not know how to create a proper citation for the origin spec given its current state and RFC 2026, please mark this as RESOLVED NEEDSINFO, and I am confident that Julian will provide the necessary spec text for you to apply. -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 8 February 2012 01:04:42 UTC