Release plan - v22.x Current

[RafaelGSS]

Draft schedule - all dates subject to change

Version	Release Date	Releaser
v22.0.0	2024-04-24	@RafaelGSS / @marco-ippolito
v22.1.0	2024-05-02	@aduh95 / @targos
v22.2.0	2024-05-15	@targos
v22.3.0	2024-06-11	@RafaelGSS

[marco-ippolito]

I'll be able to volunteer for the next releases on 22

[RafaelGSS]

Feel free to put in the agenda

[aduh95]

I can volunteer to prepare a release this week if there is a volunteer to promote it (because the release proposal for 22.0.0 was frozen some time in advance, there are commits that have landed two weeks ago which haven't made it to a release).

[targos]

It depends on the exact date but I can probably be there to promote it. I think we should wait for the npm fix to prepare a release though.

[aduh95]

Sounds good. I'm probably going to start preparing the release without waiting, as it's my first one ever, I assume I may need to start over anyway – and we can probably wait for the fix to land before doing the actual release

[marco-ippolito]

Ok Ill take another release line, please add yourself to the agenda

[targos]

I'll prepare a release next week.

[RafaelGSS]

I will prepare a release next week

[GeoffreyBooth]

@RafaelGSS when’s the latest that something can land on main while being in 22.3.0? See nodejs/TSC#1566 (comment). I’d like to get nodejs/node#53200 landed in time for 22.3.0 so that we don’t need to revert nodejs/node#52706, assuming that people are okay with the final version of nodejs/node#53200 going out in 22.3.0.

[RafaelGSS]

Usually, we create the proposals a day or two before the release date. I won't be able to release Node.js 22.3.0 tomorrow as I'll be travelling. I could do it on Friday, but I know this affects vendors' updates, so it's reasonable to postpone the next release to next Tuesday.

In other words, I'll cut off the release between Friday and Monday.