For TC39 features, we often split into two parts, one implementation bug and one shipping bug. This allows us to test the feature at stage 3 until we are sure that it is ready, as there may be web compatibility issues that crop up in nightly. This is especially true for adding methods to builtins. This corresponds with sending an "Intent to Prototype" email to the mailing list. Once the testing is finished, we merge a "ship" bug and send an "intent to ship". If the question is rather "when" will it ship, we have had it in nightly for a month now and there haven't been issues, so I will probably do it next week.
Bug 1711872 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
For TC39 features, we often split into two parts, one implementation bug and one shipping bug. This allows us to test the feature at stage 3 until we are sure that it is ready, as there may be web compatibility issues that crop up in nightly. This is especially true for adding methods to builtins. This corresponds with sending an "Intent to Prototype" email to the mailing list. Once the testing is finished, we merge a "ship" bug and send an "intent to ship". If the question is rather "when" will it ship, we have had it in nightly for a month now and there haven't been issues, so I will probably do it next week. This typically depends on the feature, sometimes we don't unflag until they go to stage 4 or are about to. This one is pretty simple so we can signal higher confidence by shipping sooner.
For TC39 features, we often split into two parts, one implementation bug and one shipping bug. This allows us to test the feature at stage 3 until we are sure that it is ready, as there may be web compatibility issues that crop up in nightly. This is especially true for adding methods to builtins. This corresponds with sending an "Intent to Prototype" email to the mailing list. Once the testing is finished, we merge a "ship" bug and send an "intent to ship". If the question is rather "when" will it ship, we have had it in nightly for a month now and there haven't been issues, so I will probably do it next week. This typically depends on the feature, sometimes we don't unflag until they go to stage 4 or are about to.
For TC39 features, we often split into two parts, one implementation bug and one shipping bug. This allows us to test the feature at stage 3 until we are sure that it is ready, as there may be web compatibility issues that crop up in nightly. This is especially true for adding methods to builtins. This corresponds with sending an "Intent to Prototype" email to the mailing list. Once the testing is finished, we merge a "ship" bug and send an "intent to ship". If the question is rather "when" will it ship, we have had it in nightly for a month now and there haven't been issues, so I will probably do it next week. This typically depends on the feature, sometimes we don't unflag until they go to stage 4 or are about to -- for others if we are certain we might ship right away.
For TC39 features, we sometimes split into two parts, one implementation bug and one shipping bug. This allows us to test the feature at stage 3 until we are sure that it is ready, as there may be web compatibility issues that crop up in nightly. This corresponds with sending an "Intent to Prototype" email to the mailing list. Once the testing is finished, we merge a "ship" bug and send an "intent to ship". If the question is rather "when" will it ship, we have had it in nightly for a month now and there haven't been issues, so I will probably do it next week. This typically depends on the feature, sometimes we don't unflag until they go to stage 4 or are about to -- for others if we are certain we might ship right away.