From 6bf13e4eef7a54d8408627a9ef5278c3bde96433 Mon Sep 17 00:00:00 2001 From: "Daniel D. Beck" Date: Tue, 1 Jul 2025 11:41:17 +0200 Subject: [PATCH 1/3] Revise "Addition of browsers" data guideline This adds some details that reflects contemporary considerations, especially the increasing automation of BCD browser and support data. --- docs/data-guidelines/browsers.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/docs/data-guidelines/browsers.md b/docs/data-guidelines/browsers.md index 4bdd39629a600b..b718235c823ef7 100644 --- a/docs/data-guidelines/browsers.md +++ b/docs/data-guidelines/browsers.md @@ -50,14 +50,16 @@ To add a new Node.js release: ## Addition of browsers -BCD's [owners](../../GOVERNANCE.md) may choose to adopt a new browser or engine. To add a new browser to BCD, we need evidence of (in decreasing order of importance): +BCD's [owners](../../GOVERNANCE.md) may choose to adopt a new browser or engine. To add a new browser to BCD, we require machine-readable release information, including version numbers, release dates, links to release notes or changelogs, and (if applicable) underlying engine version numbers. -- a compelling downstream-consumer story (e.g., MDN or caniuse express an interest, or someone is planning to do something with the data that might plausibly grow BCD's reach) -- reviewers (e.g., two or more people with interest and ability to test data relating to new and existing releases, or at least one reviewer acting on behalf of the vendor) -- a release process allowing BCD to publish stable release information in a `browsers/` file (containing release notes with version numbers and dates) +In addition to the hard requirement of machine-readable release information, we also need evidence of: + +- a compelling downstream-consumer story (e.g., MDN or caniuse express an interest in showing the data to developers or someone is planning to do something with the data that might plausibly grow BCD's reach beyond those sites) +- a compelling data-automation story (e.g., using [mdn-bcd-collector](https://mdn-bcd-collector.gooborg.com/) to generate data updates) +- reviewer capacity (e.g., two or more volunteers with the interest and ability to review data change relating to new and existing releases, or at least one reviewer acting on behalf of the vendor) - documentation (e.g., how to get and test a feature in that browser, links to resources that might help with it, etc.) -This decision was proposed in [#7238](https://github.com/mdn/browser-compat-data/issues/7238) and adopted in [#7244](https://github.com/mdn/browser-compat-data/pull/7244). +This decision was proposed in [#7238](https://github.com/mdn/browser-compat-data/issues/7238), adopted in [#7244](https://github.com/mdn/browser-compat-data/pull/7244), and revised in [#27213](https://github.com/mdn/browser-compat-data/pull/27213). ## Removal of browsers From 550ef30dccf7acb48d8e4b3f117b2ad5b6e9767b Mon Sep 17 00:00:00 2001 From: "Daniel D. Beck" Date: Tue, 1 Jul 2025 12:10:32 +0200 Subject: [PATCH 2/3] Fix collector URL Co-authored-by: Florian Scholz --- docs/data-guidelines/browsers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/data-guidelines/browsers.md b/docs/data-guidelines/browsers.md index b718235c823ef7..b4759dd8d425e6 100644 --- a/docs/data-guidelines/browsers.md +++ b/docs/data-guidelines/browsers.md @@ -55,7 +55,7 @@ BCD's [owners](../../GOVERNANCE.md) may choose to adopt a new browser or engine. In addition to the hard requirement of machine-readable release information, we also need evidence of: - a compelling downstream-consumer story (e.g., MDN or caniuse express an interest in showing the data to developers or someone is planning to do something with the data that might plausibly grow BCD's reach beyond those sites) -- a compelling data-automation story (e.g., using [mdn-bcd-collector](https://mdn-bcd-collector.gooborg.com/) to generate data updates) +- a compelling data-automation story (e.g., using [mdn-bcd-collector](https://github.com/openwebdocs/mdn-bcd-collector) to generate data updates) - reviewer capacity (e.g., two or more volunteers with the interest and ability to review data change relating to new and existing releases, or at least one reviewer acting on behalf of the vendor) - documentation (e.g., how to get and test a feature in that browser, links to resources that might help with it, etc.) From e0ae97560795e01088be71a9ce9bb7e42eded484 Mon Sep 17 00:00:00 2001 From: "Queen Vinyl Da.i'gyu-Kazotetsu" Date: Fri, 18 Jul 2025 13:03:10 -0700 Subject: [PATCH 3/3] Update browsers.md Co-authored-by: Claas Augner <495429+caugner@users.noreply.github.com> --- docs/data-guidelines/browsers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/data-guidelines/browsers.md b/docs/data-guidelines/browsers.md index b4759dd8d425e6..ceb3021b86d534 100644 --- a/docs/data-guidelines/browsers.md +++ b/docs/data-guidelines/browsers.md @@ -56,7 +56,7 @@ In addition to the hard requirement of machine-readable release information, we - a compelling downstream-consumer story (e.g., MDN or caniuse express an interest in showing the data to developers or someone is planning to do something with the data that might plausibly grow BCD's reach beyond those sites) - a compelling data-automation story (e.g., using [mdn-bcd-collector](https://github.com/openwebdocs/mdn-bcd-collector) to generate data updates) -- reviewer capacity (e.g., two or more volunteers with the interest and ability to review data change relating to new and existing releases, or at least one reviewer acting on behalf of the vendor) +- reviewer capacity (e.g., two or more volunteers with the interest and ability to review data changes relating to new and existing releases, or at least one reviewer acting on behalf of the vendor) - documentation (e.g., how to get and test a feature in that browser, links to resources that might help with it, etc.) This decision was proposed in [#7238](https://github.com/mdn/browser-compat-data/issues/7238), adopted in [#7244](https://github.com/mdn/browser-compat-data/pull/7244), and revised in [#27213](https://github.com/mdn/browser-compat-data/pull/27213).