Time for next release?

[mhdawson]

It will have been 2 months from the last release next week. We should probably start thinking about doing a release.

So far I think we'd want to address the following before releasin:

• Intermittent failure in ThreadSafe function #906

[mhdawson]

I'm thinking we should plan 2 releases. One fairly soon, and then one after April 30 to drop support for Node.js. This would make sure the last 3.x version is up to date.

@NickNaso what do you think of a release April 15th, and then a release May 6th with the only change being dropping support for 8.x?

[NickNaso]

Hi @mhdawson,
I agree with you about the next releases for node-addon-api. To recap we will have two new releases:

• 3.2.0 that will be the last 3.x and we should deliver it within 15th April (We should define what we need to keep in this release).
• 4.0.0 Removes support for Node.js 8 and deliver it within 6th May (We should define what we need to drop)

We can open two new issues to track the works on both releases.

[gabrielschulhof]

From today's Node-API meeting:

The APIs in napi-inl.deprecated.h are good candidates for removal in 4.0.0, however, how shall we announce that we are removing them? Can we even remove them? Some folks might still be using them.

We should likely also resolve the issue of what to do when we attempt to throw an exception during environment shutdown before making a release.

Another problem we might want to solve before the next release is #906.

[mhdawson]

I'm thinking we should still leave "napi-inl.deprecated.h". I don't think they have been causing us any maintenance issues and I think we probably want to discuss more/message more if we are going to do it in advance.

In my mind the main or possibly only thing that we need in 4.0.0 is dropping support for Node.js 10.x once it is out of LTS.

[mhdawson]

@nodejs/node-api you can check out the discussion in #906 but the conclusion I have is that the intermittent failures we are seeing in the CI are not related to node-addon-api, but instead changes that are needed in core. Therefore we should be ok to move ahead with the releases we'd planned.

[NickNaso]

I'm starting to work on release 3.2.0.

[NickNaso]

CI:

Version	Job	Status
v16.x	https://ci.nodejs.org/job/node-test-node-addon-api-new/4132/	✓
v14.x	https://ci.nodejs.org/job/node-test-node-addon-api-new/4131/	✓
v12.x	https://ci.nodejs.org/job/node-test-node-addon-api-new/4130/	✓

[NickNaso]

The version 3.2.0 has been released. Enjoy.

[NickNaso]

I'm starting to prepare the release 3.2.1.

[NickNaso]

CI:

Version	Job	Status
v16.x	https://ci.nodejs.org/job/node-test-node-addon-api-new/4188/	✓
v14.x	https://ci.nodejs.org/job/node-test-node-addon-api-new/4187/	✓
v12.x	https://ci.nodejs.org/job/node-test-node-addon-api-new/4186/	✓
v10.x	https://ci.nodejs.org/job/node-test-node-addon-api-new/4185/	✓

Version	Job	Status
v16.x	https://ci.nodejs.org/job/node-test-node-addon-api-new/4195/	✓
v14.x	https://ci.nodejs.org/job/node-test-node-addon-api-new/4194/	✓
v12.x	https://ci.nodejs.org/job/node-test-node-addon-api-new/4193/	✓
v10.x	https://ci.nodejs.org/job/node-test-node-addon-api-new/4192/	✓

[NickNaso]

Hi everybody,
I want to work on release 4.0.0. From the last release 3.2.1 we have two noew commits:

• fed1353
• b75afc4

May I proceed to create the new release removing the support for Node.js v10?
@nodejs/node-api

[NickNaso]

CI:

Version	Job	Status
v16.x	https://ci.nodejs.org/job/node-test-node-addon-api-new/4265/	✓
v14.x	https://ci.nodejs.org/job/node-test-node-addon-api-new/4266/	✓
v12.x	https://ci.nodejs.org/job/node-test-node-addon-api-new/4267/	✓

CI:

Version	Job	Status
v16.x	https://ci.nodejs.org/job/node-test-node-addon-api-new/4268/	✓
v14.x	https://ci.nodejs.org/job/node-test-node-addon-api-new/4269/	✓
v12.x	https://ci.nodejs.org/job/node-test-node-addon-api-new/4270/	✓

[NickNaso]

The release 4.0.0 has been published.

[NickNaso]

I think that I can close the issue, if not feel free to reopen it.