Release plan - v22.x Active LTS

[RafaelGSS]

Draft schedule - all dates subject to change

Version	Release Date	Releaser
v22.11.0 (LTS transition)	2024-10-29	@richardlau
v22.12.0	2024-12-03	@ruyadorno
v22.13.0	2025-01-07	@ruyadorno
v22.13.1 (security)	2025-01-21	@RafaelGSS
v22.14.0	2025-02-11	@aduh95
v22.x.x	2025-03-18
v22.x.x	2025-04-15
v22.x.x	2025-05-13
v22.x.x	2025-06-10
v22.x.x	2025-07-08
v22.x.x	2025-08-05
v22.x.x	2025-09-02
v22.x.x	2025-09-30
v22.x.x (Maintenance transition)	2025-10-21	No release

Current

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
v22.4.0	2024-07-02	@targos
v22.4.1	2024-07-08	@RafaelGSS (Security)
v22.5.0	2024-07-17	@aduh95 / @RafaelGSS
v22.5.1	2024-07-19	@richardlau
v22.6.0	2024-07-30	@RafaelGSS
v22.7.0	2024-08-20	@RafaelGSS
v22.8.0	2024-09-03	@RafaelGSS
v22.9.0	2024-09-18	@RafaelGSS
v22.10.0	2024-10-16	@aduh95

[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.