Make next release semver-major/Request for 2.x release with backports

[gabrielschulhof]

@addaleax pointed out that because of the removal of support for v6.x and v8.x the next release must be semver-major.

[NickNaso]

Hi @gabrielschulhof ,
I agree with you we can discuss about it at next N-API meeting and then proceed to make the release 3.0.0.

[mhdawson]

Makes sense to me.

[mhdawson]

Discussed in the N-API team meeting today. We can wait until we have enough to do a release, and then we'll make it SemVer major at that point.

[legendecas]

Would like #594 and #653 to be addressed before we can make next semver-major release since they are likely to introduce breaking changes.

[blagoev]

when will be the next version released? There are a lot of critical fixes committed in master and pending release. Like memory leaks and crashes.

[mhdawson]

@gabrielschulhof, @NickNaso We should probably add that to the agenda for the next N-API team meeting.

[addaleax]

Bump? It’s been 5 months since the last release…

[legendecas]

@addaleax We are waiting on the checklist here #689 to be all closed.

[addaleax]

@legendecas That’s understandable, but… holding up releases like that is not great in terms of DX and kind of makes me want to start maintaining a fork of this repo that actively releases 😬

[blagoev]

We have done a release based of a fork. IMO critical fixes and memory leaks should not wait for other features too much. Still it is what it is, and we are waiting for node-addon-api v3 to do a proper release.

[addaleax]

Right, I feel like we should at least have another v2.x release here. Mixing in a breaking change with critical fixes doesn’t seem like a great choice.

[blagoev]

Well on this one the fixes required breaking changes. My comment was about the new features that are planned and still holding up the release, but I think the team knows better.