Publishing test manifests for web features #4602
Description
In gh-4599, we're adding some metadata so that the web-features project can better integrate with Test262. Most consumers of this metatdata will be interested in the result of applying the classifications--that is, a direct mapping of web features to test names. While every consumer can generate this mapping by interpreting the classification rules, it's preferable (both in terms of efficiency and correctness) for this mapping to be generated once and shared among consumers. Ideally this mapping would be generated for every commit of Test262's main branch.
There are many options for how this project could facilitates the publication of these mappings. Among them are:
- by generating them in a GitHub Action and uploading them to GitHub using the "Release" functionality for this repository (this is the approach taken by the Web Platform Tests project)
- by generating them in a GitHub Action and uploading them to GitHub using the "Release" functionality for some other repository
- by notifying some external service in a GitHub Action (which can itself generate the mappings and publish them wherever it sees fit)
The advantage of the first two options is that failures in the publication process are localized to the source of the problem. They also give the Test26 maintainers more control over the structure of the classification schema (since they would be shifting the public contract from to a simpler machine-readable "identifier-to-filename" mapping).
We've briefly discussed some of these approaches during the routine Test262 maintainers' call, but we haven't agreed on which path to take. Can you folks weigh in with your preference?