Range linter: Disallow ranged values after 2020-01-01

[Elchi3]

What type of issue is this?

Linter issue

What is the issue?

Ranged values are currently allowed for browser versions released two years or earlier.

What behavior were you expecting?

If you set the linter to four years or earlier, it still passes. We should enforce that, so that we can make the guarantee that BCD will always report a real (non-ranged) version for as many years as possible.

What version(s) of BCD is the issue present in?

• [X] The current BCD release
• [X] The current version of the main branch

Do you have anything more you want to share?

It doesn't pass for:

• 5 years: 832 errors (≤79 for Edge, ≤83 for Chrome, ≤72 for Firefox, and ≤13.1 for Safari would no longer be allowed)
• 6 years: 913 errors (≤18 for Edge would no longer be allowed)
• 7 years: 930 errors
• 8 years: 953 errors
• 9 years: 957 errors
• 10 years: 1793 errors (≤37 for WebView Android would no longer be allowed)

cc @foolip @ddbeck

[ddbeck]

We should enforce that, so that we can make the guarantee that BCD will always report a real (non-ranged) version for as many years as possible.

Agreed. Though I'd like to suggest going one step further and pinning those versions that define the 4-year cut off, rather than having a rolling X-year window. That way no new uncertainties would emerge (e.g., a year from now, you wouldn't be allowed to add a ranged value to a 2020 release).

[Elchi3]

For reference, Philip and Daniel discussed using a cut off before: https://github.com/mdn/browser-compat-data/pull/19146#pullrequestreview-1342350432

[queengooborg]

Unfortunately, a recent update to the web extensions data has now introduced a range that is within two years, so we are no longer able to switch to a longer date at this time. Currently, it is only one single range, so we may be able to prioritize researching a proper version number and replace the range.