RE: Outstanding PRs and changes post level 1

For the io version[1], will that always reflect master? To see the REC version of the spec, users will want to go to the github repo branch[2]?

[1]: https://w3c.github.io/webdriver/webdriver-spec.html

[2]: https://github.com/w3c/webdriver/tree/level-1


From: Simon Stewart [mailto:simon.m.stewart@gmail.com]
Sent: Wednesday, October 25, 2017 8:35 AM
To: Andreas Tolfsen <ato@sny.no>
Cc: public-browser-tools-testing <public-browser-tools-testing@w3.org>
Subject: Re: Outstanding PRs and changes post level 1

I asked on the channel, and Mike said it was fine to go ahead and create a branch.

https://github.com/w3c/webdriver/tree/level-1 is now available for the spec work as we finish Level 1, and the living spec is still on master.

Simon

On Tue, Oct 24, 2017 at 7:27 PM, Simon Stewart <simon.m.stewart@gmail.com<mailto:simon.m.stewart@gmail.com>> wrote:
Hi,

TBH, I thought we'd have reached REC right now so this would be a moot point. Given that we're not, I'm fine with creating a branch for the PR work. It'd be nice to move the spec forward again :)

If Mike gives us the go-ahead, we can get going ASAP.

Simon


On Tue, Oct 24, 2017 at 11:13 AM, Andreas Tolfsen <ato@sny.no<mailto:ato@sny.no>> wrote:
At the time of writing there are 22 outstanding PRs for the
specification.  It is important to us as a vendor that the living
standard reflects the reality of the implementations, and some of
the PRs contains useful clarifications we would like to see in the
specification.

I understand the editors are working on preparing a snapshot of the
document for CR/REC, meaning it will be frozen with limited ability
to make changes, but because Mozilla—and I imagine most other
vendors—follow the living document (last changed 23 October) [2]
rather than the TR (dated 30 March) [3], it doesn’t make sense to
put a halt to further changes aimed at post level 1.

I would suggest branching off level 1 to a separate branch so we can
continue iterating on the master branch.  If there are particularly
important bug fixes that needs to make level 1 they can be cherry
picked or backported.

 [1] https://github.com/w3c/webdriver/pulls

 [2] https://w3c.github.io/webdriver/webdriver-spec.html

 [3] https://www.w3.org/TR/webdriver/