W3C home > Mailing lists > Public > public-browser-tools-testing@w3.org > October to December 2017

RE: Outstanding PRs and changes post level 1

From: John Jansen <John.Jansen@microsoft.com>
Date: Wed, 15 Nov 2017 22:12:18 +0000
To: Andreas Tolfsen <ato@sny.no>, public-browser-tools-testing <public-browser-tools-testing@w3.org>
CC: Simon Stewart <simon.m.stewart@gmail.com>
Message-ID: <BN6PR21MB0129F9A597173FE7AC759793F1290@BN6PR21MB0129.namprd21.prod.outlook.com>
Thanks for the response, Andreas
> Also sprach John Jansen:
> > 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
> My understanding is that the latest approved CR (soon to be REC, fingers
> crossed) will be readable here:
> 	https://www.w3.org/TR/webdriver/

I thought we resolved on it being something like http://www.w3.org/TR/webdriver/1/ (or similar).
But I (obviously) could be wrong.

> Note that the latest document available under /TR might not exactly reflect
> what is on the level-1 branch due to W3C voodoo.
> When we publish the next PR, after we are done with v1, I believe w3.org
> provides a snapshotting feature to move back in time to see earlier PRs.


I'm primarily concerned with shortcuts here, so specifically: no matter what happens with snapshots for the W3C,
I hope that the w3c.github.io link is always the LIVING document and not the v1 recommendation (which no one
will care about a day after it's published).

Received on Wednesday, 15 November 2017 22:12:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:09:56 UTC