-
Notifications
You must be signed in to change notification settings - Fork 555
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release plan - v22.x Current #1001
Comments
I'll be able to volunteer for the next releases on 22 |
Feel free to put in the agenda |
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). |
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. |
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 |
Ok Ill take another release line, please add yourself to the agenda |
I'll prepare a release next week. |
I will prepare a release next week |
@RafaelGSS when’s the latest that something can land on |
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. |
I'll prepare v22.4.0 |
Draft schedule - all dates subject to change
The text was updated successfully, but these errors were encountered: