-
Notifications
You must be signed in to change notification settings - Fork 551
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
Volunteering for next v11.x #395
Comments
I think @BridgeAR is preparing a v11.x release for this week. |
@targos I think the idea was that @BridgeAR would do this week and @BethGriggs would do next week |
OK, fine by me if there are enough new commits next week to justify a release :) |
I opened #397 to track all future releases of v11.x. I suggest we close this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As discussed in #393, new releasers need to prep and release at least one Current Node.js release before promoting an LTS release.
I volunteer to do the next v11.x (maybe next week?)
/cc @MylesBorins
The text was updated successfully, but these errors were encountered: