W3C home > Mailing lists > Public > public-web-perf@w3.org > March 2017

Adopting a dual spec/testing process for webperf specs

From: Philippe Le Hégaret <plh@w3.org>
Date: Wed, 29 Mar 2017 10:24:28 -0400
To: "public-web-perf@w3.org" <public-web-perf@w3.org>
Cc: Rick Byers <rbyers@google.com>
Message-ID: <217c9085-1e32-1df7-ae54-8db3ec63cc8b@w3.org>
Our specifications and our tests are out of sync. Most often, the tests 
are behind (eg Beacon) and sometimes, the tests are ahead (eg User 
Timing). This is costing us dearly in the long run imho (eg TAO, 

I'd like to propose that the Working Group adopts a dual spec/testing 
process, similar to the one applied in the pointer events working group 
[1] and the whatwg [2]:

Normative spec changes are generally expected to have a corresponding 
pull request in web-platform-test. Outstanding test work is tracked via 
issues in this repository and issues generally remain open until both 
spec and test changes land. If one PR is approved but the other needs 
more work, add the 'do not merge yet' label or, in web-platform-tests, 
the 'status:needs-spec-decision' label.



[1] https://github.com/w3c/pointerevents/blob/gh-pages/README.markdown
[2] https://github.com/whatwg/meta/blob/master/TEAM.md
Received on Wednesday, 29 March 2017 14:24:38 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 29 March 2017 14:24:39 UTC