-
Notifications
You must be signed in to change notification settings - Fork 568
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 - v15.x Current #621
Comments
Once my name gets merged to the releasers list, I can pick up a 15.x release in November 👍🏼 |
I signed up for the first 15.x release in November! |
I was thinking it would be good to get a v15.x release out today or tomorrow to land some moduels changes we might still want to see go out on 12.x Any concerns? |
I'm preparing v15.1.0 right now. |
Signing up for a v15 release next month 😊 |
@nodejs/releasers Since there is a 15.x.x security release on Monday (1/4), does the 15.x release still go out on Tuesday (1/5)? |
@danielleadams, i'd suggest deferring it slightly to avoid having back-to-back releases - I'd suggest either 12th Jan or maybe even 7th Jan. Whichever dates work for your schedule :) |
Alright sounds good! I changed the next 15.x release to 1/12 |
Since v15.4.0 went out just a few days ago, should we push the release a bit? cc @MylesBorins |
@codebytere, IMO we should consider dropping the last scheduled release rather than delaying, as Node.js 16 will be released on Tues 20th. One of the oddities of the major release process is that we run the branch-diff between the most recent Node.js 15 and the |
@BethGriggs happy to just remove myself from the schedule then? |
Yeah, I think that makes sense. As you mentioned it's only been a few days since the last release so that seems appropriate in this case |
Draft schedule - all dates subject to change
The text was updated successfully, but these errors were encountered: