Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Identify when a TR draft exists for a spec only known as editors draft #62

Closed
dontcallmedom opened this issue May 28, 2020 · 0 comments · Fixed by #108
Closed

Identify when a TR draft exists for a spec only known as editors draft #62

dontcallmedom opened this issue May 28, 2020 · 0 comments · Fixed by #108

Comments

@dontcallmedom
Copy link
Member

When a spec goes to a FPWD, and assuming it was being tracked as an editor draft by browser-specs, we would want to update the entry in the list of specs to point to the TR draft.

Ideally, this would happen when running the crawl on editors draft - we should check if the TR url exists, and file an issue if it does.
dontcallmedom added a commit that referenced this issue Jun 10, 2020
@dontcallmedom
Add comparison with data extracted from TR
ad960ea 
probably helps with #62
@dontcallmedom dontcallmedom mentioned this issue Jun 10, 2020
Merged
tidoust added a commit to tidoust/browser-specs that referenced this issue Jun 11, 2020
@tidoust
Add tests to compare base URL with release/nightly URL
fc50414 
The base URL should either match the release URL if there is one or the nightly
URL otherwise. New tests will fail when there are entries in `index.json` for
which that is not the case.

The first test should also help with identification of situations where a FPWD
was published, and is known to Specref but not to us (w3c#62).

Note that, as opposed to other tests that only depend on internal code logic,
the second test may fail because external sources (Specref in practice) need to
be fixed to return the right nightly URL. Fixing the problem at the source may
take some time.
tidoust added a commit to tidoust/browser-specs that referenced this issue Jun 11, 2020
@tidoust
Add tests to compare base URL with release/nightly URL
54b9623 
The base URL should either match the release URL if there is one or the nightly
URL otherwise. New tests will fail when there are entries in `index.json` for
which that is not the case.

The first test should also help with identification of situations where a FPWD
was published, and is known to Specref but not to us (w3c#62).

Note that, as opposed to other tests that only depend on internal code logic,
the second test may fail because external sources (Specref in practice) need to
be fixed to return the right nightly URL. Fixing the problem at the source may
take some time.
@tidoust tidoust mentioned this issue Jun 11, 2020
Closed
dontcallmedom added a commit that referenced this issue Jun 18, 2020
@dontcallmedom
Make sure to detect TR versions of specs we're otherwise tracking
b6a235a 
close #62
@dontcallmedom dontcallmedom mentioned this issue Jun 18, 2020
Merged
tidoust pushed a commit that referenced this issue Jun 18, 2020
@dontcallmedom
Make sure to detect TR versions of specs we're otherwise tracking (#108)
7cefbbc 
close #62
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Make sure to detect TR versions of specs we're otherwise tracking w3c/browser-specs
1 participant
@dontcallmedom