Closed Bug 1170709 Opened 8 years ago Closed 7 years ago

[Compat Data][Importer] Parse CompatNightly

Categories

(developer.mozilla.org Graveyard :: General, defect)

All
Other
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: fs, Assigned: jwhitlock)

Details

(Keywords: in-triage, Whiteboard: [specification][type:bug])

What did you do?
================
1. Looked at https://browsercompat.herokuapp.com/importer/4720 and others.
2. 
3. 

What happened?
==============
{{CompatNightly}} is not parsed.

What should have happened?
==========================
Import the version as "nightly" or "future release" for this feature.

Is there anything else we should know?
======================================
We have a lot of documented things that are available in the Firefox Nightly channel only. Is there another way to fix these import parsing errors?
Blocks: 1132269
The macro has a parameter, btw.
E.g. {{CompatNightly("firefox")}}
See https://developer.mozilla.org/en-US/docs/Template:CompatNightly
I think Firefox Nightly would be version=null, status=beta.  This probably requires the API changes in bug 1160214 (Support unknown future versions) before the scraper can support it.
fsholz: what is the difference between CompatNightly("firefox") and Firefox 42?  Could instances of CompatNightly all be replaced by specific future version numbers?
Flags: needinfo?(fscholz)
> fscholz: what is the difference between CompatNightly("firefox") and Firefox
> 42?  

Some experimental features are only appearing in the Nightly version of Firefox. It is basically a flag depending on the "train". These features will stay in Nightly and are not riding the train into beta or release version of Firefox. Every 6 weeks versions are bumped. The Nightly-only features stay in Nightly with the new version. The version of Nightly is not really important. We refer to it as "Nightly" without a version.

> Could instances of CompatNightly all be replaced by specific future version numbers?
No.
Flags: needinfo?(fscholz)
Code to handle {{CompatNightly}} is submitted in PR #41:

https://github.com/mozilla/web-platform-compat/pull/41

It becomes a Version resource with version="nightly" and status="future".

The subject page now imports cleanly:

https://browsercompat.herokuapp.com/importer/4720

I haven't run a full reparse of all the imported pages, just that one.
No longer blocks: 1132269
Summary: Parse CompatNightly → [Compat Data][Importer] Parse CompatNightly
Assignee: nobody → jwhitlock
Status: NEW → ASSIGNED
Commits pushed to master at https://github.com/mozilla/web-platform-compat

https://github.com/mozilla/web-platform-compat/commit/71b7c960a60b055b12db71bf48aa453d436b59ab
bug 1170709 - Add --skip-deletes option

For tools/load_spec_data.py, if a Maturity becomes unused, the default
is to delete it.  The --skip-deletes option syncs additions and changes
but not deletes.

https://github.com/mozilla/web-platform-compat/commit/2a643f726fb63b6a353f25ac5b9df3328bc95fb3
fix bug 1170709 - {{CompatNightly}} and others

When scraping compatibility cells, {{CompatNightly}} is translated into
a version with version "nightly" and status "future".  Also, other
KumaScript such as {{CompatNo}} is translated into the new "unknown
version" with version "current" and status "current".
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.