[csswg-drafts] Update CONTRIBUTING.md to match how the testing process really works

foolip has just created a new issue for https://github.com/w3c/csswg-drafts:

== Update CONTRIBUTING.md to match how the testing process really works ==
In the [conclusions](https://docs.google.com/document/d/1kFYTqUMEbo9p87i6wAzORoicMWgHsuYwL2CgtvdhDaE/edit#heading=h.m00sri6scfj2) I wrote:
> CSS specs came up three times. The WG decision → spec update → [Needs Testcase (WPT)](https://github.com/w3c/csswg-drafts/issues?utf8=%E2%9C%93&q=is%3Aissue+label%3A%22Needs+Testcase+%28WPT%29%22+) process means that tests aren’t generally expected to be written at the time of the spec change and in our investigation we normally dropped in between the “spec update” and “test written” stage, and we haven’t looked into when the tests normally end up being written. Whatever the process is, it’s not what is described in [CONTRIBUTING.md](https://github.com/w3c/csswg-drafts/blob/master/CONTRIBUTING.md#tests).

CONTRIBUTING.md was updated in https://github.com/w3c/csswg-drafts/pull/1767, see that PR for background.

I think CONTRIBUTING.md now matches neither how things actually work or the aspiration, in particular "Typically, both PRs will be merged at the same time" doesn't make sense since spec changes aren't done via PRs and the test updates normally don't happen at the same time.

I think the current process is to close all "Needs Testcase (WPT)" issues for spec before publishing it as CR or higher next time, but better that someone who's in the loop spells it out than me guessing.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2503 using your GitHub account

Received on Thursday, 5 April 2018 10:41:09 UTC