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

add a new testing stage #37

Closed michaelficarra closed 11 months ago

michaelficarra commented 11 months ago

To be used as a basis for the ongoing discussion of a new stage at the upcoming TC39 meeting.

michaelficarra commented 11 months ago

This should be good to merge as-is.

leobalter commented 11 months ago

Ideas for a subsequent change (another PR), with the repetition of "testing, implementation, or usage experience" we might set these as a definition for "feature adoption" (name is up for bikeshed), so we only repeat the shorter verson.

E.g.: 

-The solution is complete and no further work is possible without feedback from tests, implementations, or usage. No changes to the proposal will be requested aside from those elicited through testing, implementation, or usage experience.
+The solution is complete and no further work is possible without feedback from tests, implementations, or usage. No changes to the proposal will be requested aside from those elicited through feature adoption.

+Feature adoption for proposals comprehends the experience observed by testing results, implementation, and/or usage.

This change must not block the progress/acceptance of this PR as it only serves as cosmetic/editorial.

michaelficarra commented 11 months ago

These suggestions are great, but for process document changes, I don't feel comfortable merging anything other than the exact wording that was agreed upon. Unlike with how the committee delegates authority to the editor group to execute what they understand to be the committee's will, changes to this document are approved explicitly. Since I'm making a follow-up anyway, I'll incorporate these suggestions into that. But next time, please review the PR before it is approved.