/cc @nodejs/backporters @nodejs/releasers ...

CI: https://ci.nodejs.org/job/node-test-pull-request/35680/

Landed in 3aeaaea

@jasnell we usually do some degree of consensus building with @nodejs/lts prior to backporting semver-minor commits and we generally have it back longer than 14 days prior to a backport (more often multiple months).

Is this an experimental feature?

Feel free to revert if necessary

I'm preparing a patch release of v14 for this week (the plan was to keep this one intentionally small to just address some bugs and pull in an npm update). For ease of preparing the patch release - I'll probably temporarily drop the commit from the staging branch and reopen.

If there are no concerns from @nodejs/lts, i'll aim to re-land on staging after the patch release has gone out? The following/February release is scheduled to be a minor (nodejs/Release#567), and by the time of that release it'll probably have been out in v15 for a while (1 month+).

@MylesBorins @BethGriggs ... What's the timeline on this landing in 14.x again?

We do not yet have a volunteer to prepare the next planned release of Node.js 14. The upcoming security release has pushed the schedule out a little too.

We can pull this into staging ready to go out in the next release (which is due to be a minor). But unfortunately the actual release might be a while off, bearing in mind we'll need volunteer(s), and we've previously aimed for 2-3 weeks release candidate phase for minors.

(It's on my list to try and land some commits on v14.x-staging, but I cannot commit the time to preparing the whole release atm.)

@nodejs/releasers ... any updates on when this might land in 14.x?

@jasnell when someone takes the time to prepare the next semver-minor release.

CI: https://ci.nodejs.org/job/node-test-pull-request/37654/

CI: https://ci.nodejs.org/job/node-test-pull-request/37682/

Landed in 08f9130