Release a v5.2.1?

[ljharb]

v5.2.0 has a breaking repl bug (#4257). It was fixed in #4215 with a two-line change.

Could this be merged into the 5.2.x line and released as v5.2.1, so that the 5.2.x line no longer has breaking changes that would make it deserve to be a 6.x release? Hopefully git cherry-pick 1999fdc859ec80740f64e3af1dea54acbc4d4f37 plus the release process is not a burdensome amount of work for anybody.

[Fishrock123]

cc @nodejs/release

[silverwind]

5.3.0 just got released, that should solve it.

I think we need to be a bit more agile regarding emergency releases like in this case. Having a broken REPL for over a week with a fix already in master is not ideal. Adding CTC-Agenda.

[ljharb]

@silverwind that does not solve it, because 5.2.x still has a breaking change. Please reopen this?

[ljharb]

More specifically, if 5.2.x introduces a breaking change, then node isn't being a good semver citizen.

[silverwind]

I might be wrong, but I don't think we're providing any kind of LTS for minor versions like 5.2.x yet. Ideally, 5.2.1 should've happened right after the fix got commited. From what I gather, 5.3.0 is the 'fix' now that it is released.

[Fishrock123]

I think we need to be a bit more agile regarding emergency releases like in this case. Having a broken REPL for over a week with a fix already in master is not ideal. Adding CTC-Agenda.

I think having more releasers here would probably help. Sometimes myself, Rod, and James get tied up in other things (like Node.js Interactive!).

[evanlucas]

I would definitely be interested in helping out with releases

[MylesBorins]

I would be interested in helping with release as well

[ofrobots]

If a 5.2.1 does occur, it would need #4298 as well.