From 6e84d55f110e54eff601e1ccc1a7f83cdc0f9801 Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Wed, 25 Oct 2017 21:06:47 -0700 Subject: [PATCH] clarification on runtime deprecation criteria question --- meetings/2017-10-25.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/meetings/2017-10-25.md b/meetings/2017-10-25.md index 44f39036..436646d3 100644 --- a/meetings/2017-10-25.md +++ b/meetings/2017-10-25.md @@ -71,8 +71,9 @@ * Rich had action item to take pulse of TSC as there was some suggestion that maybe we should never do it. Survey of 14 TSC memory shows there is desire to runtime deprecate at sometime in the future. - * Remaining question is what by what criteria would it get runtime deprecation. Seems - like at this point we don't know and need to take another look in 6 months. + * Remaining question is by what criteria would it get a runtime deprecation. + Rich observed that TSC appears unwilling or unable to provide specific + criteria. * stream: move prefixed files into internal/streams. [#11957](https://github.com/nodejs/node/pull/11957) * Enable explicit `.m.js` intent for ESM [#16170] (https://github.com/nodejs/node/pull/16170)