search

tc39 / process-document

Document describing the process for making changes to ECMA-262
https://tc39.es/process-document/
30 stars 18 forks source link

Require filing implementation tracking bugs after getting to stage 3? #10

Open mathiasbynens opened 7 years ago

mathiasbynens commented 7 years ago

Once a proposal reaches stage 3, it makes sense to file implementation tracking bugs for ChakraCore, JavaScriptCore, SpiderMonkey, and V8, and to link to them from the proposal repository’s README.

Can we make this a post-Stage-3-acceptance requirement? For many stage 3 proposals, it’s currently unclear if bugs have been filed against every major engine or not just by looking at the repository.

michaelficarra commented 7 years ago

Strong :-1:. This is not the responsibility of the champion or of TC39 in general. Each implementation, including minor and major ones, is responsible for tracking the standard and their development process in their own way. A wise champion may want to get involved if they want to achieve stage 4 sooner, but should not be required.

mathiasbynens commented 7 years ago

For stage 4, implementations are required — why wouldn’t you want to track implementation progress in the repository?

ljharb commented 7 years ago

I think you absolutely would want to - but it's not a requirement. If the champion decides not to track, then they may find it harder to meet the stage 4 requirements, but that's not necessarily the case.