Skip to content
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 - v12.x Maintenance #494

Closed
targos opened this issue Oct 21, 2019 · 34 comments
Closed

Release plan - v12.x Maintenance #494

targos opened this issue Oct 21, 2019 · 34 comments

Comments

@targos
Copy link
Member

targos commented Oct 21, 2019

Week Release candidate Approximative date Release Releaser
2019 - 43 2019-10-21 v12.13.0 (Active) @targos
2019 - 47 2019-11-19 2019-11-26 v12.13.1 @targos
2020 - 02 2019-12-24 2020-01-07 v12.14.1 @BethGriggs
2020 - 06 2020-02-06 v12.15.0 (Security) @BethGriggs
2020 - 07 2020-01-14 2020-02-12 v12.16.0 @targos
2020 - 08 2020-02-18 2020-02-25 v12.16.1 @MylesBorins
2020 - 13 2020-03-17 2020-04-07 v12.16.2 @codebytere
2020 - 17 2020-04-21 2020-04-28 v12.16.3 @targos
2020 - 22 2020-05-12 2020-05-26 v12.17.0 @targos
2020 - 23 - 2020-06-02 v12.18.0 (Security) @targos
2020 - 25 2020-06-09 2020-06-16 v12.18.1 @codebytere
2020 - 27 2020-06-26 2020-06-30 v12.18.2 @BethGriggs (Additional release)
2020 - 30 2020-07-14 2020-07-21 v12.18.3 @codebytere
2020 - 35 2020-09-29 2020-10-06 v12.19.0 @codebytere
2020 - 44 - 2020-11-16 v12.19.1 (Security) @BethGriggs
2020 - 45 2020-11-03 2020-11-24 v12.20.0 (Maintenance) @ruyadorno / @MylesBorins
2021 - 1 2021-01-04 v12.20.1 (Security) @richardlau
2021 - 4 2021-02-10 v12.20.2 @ruyadorno
2021 - 8 - 2021-02-23 v12.21.0 (Security) @richardlau
2021 - 13 - 2021-03-30 v12.22.0 @richardlau
2021 - 14 - 2021-04-06 v12.22.1 (Security) @MylesBorins
2021 - 26 - 2021-07-01 (Security) v12.22.2 @richardlau
2021 - 27 - 2021-07-05 v12.22.3 @richardlau
2021 - 30 - 2021-07-29 v12.22.4 (Security) @richardlau
2021 - ?? - 2021-08-25 v12.22.5 (Security) @BethGriggs
2021 - ?? - 2021-08-31 v12.22.6 (Security) @MylesBorins
2021 - ?? - 2021-10-12 v12.22.7 (Security) @danielleadams
2021 - ?? - 2021-12-16 v12.22.8 @richardlau
2022 - 02 - 2022-01-10 v12.22.9 (Security) @richardlau
2022 - ?? 2022-01-25 2022-02-01 v12.22.10 @ruyadorno
2022 - ?? - 2022-03-17 v12.22.11 (Security) @richardlau
2022 - ?? 2022-03-30 2022-04-05 v12.22.12 @richardlau
@BethGriggs
Copy link
Member

BethGriggs commented Oct 24, 2019

Previously we've aimed for one scheduled release per month, with one semver-minor release per quarter. Does it make sense to start with that for v12.x? One consideration would be that with v12.x only has 12months of Active LTS.

@MylesBorins
Copy link
Contributor

MylesBorins commented Oct 24, 2019 via email

@targos targos changed the title Release plan - v12.x LTS Release plan - v12.x Active LTS Oct 24, 2019
@targos
Copy link
Member Author

targos commented Oct 24, 2019

I added a table to the OP with this cadence. Does it look good?

@targos targos pinned this issue Oct 27, 2019
@targos
Copy link
Member Author

targos commented Oct 31, 2019

/cc @nodejs/lts

@richardlau
Copy link
Member

LGTM. Only question I have is April 2020 is Node.js 10 transitioning to maintenance (potential last minute rush to get things into 10.x) and initial Node.js 14 so whether a semver-minor for 12 in the same month would be overloading the releasers?

@BethGriggs
Copy link
Member

Looks good but I also agree with @richardlau - but maybe we can make that call closer to the time depending on Releaser availability?

@mhdawson
Copy link
Member

mhdawson commented Nov 1, 2019

+1 to proposed schedule

@BethGriggs
Copy link
Member

BethGriggs commented Jan 27, 2020

Thoughts on whether v12.15.0(nodejs/node#31368) should be delayed due to https://nodejs.org/en/blog/vulnerability/february-2020-security-releases/? /cc @nodejs/releasers @nodejs/lts @targos

@targos
Copy link
Member Author

targos commented Jan 27, 2020

I think we should reschedule it. Maybe the week after the security release?

@MylesBorins
Copy link
Contributor

+1 on delaying until the week after the security release.

There are a couple module related PRs that landed in the last 13.x release we should consider including. I'll work on backporting this week.

@ggoodman
Copy link

ggoodman commented Jan 28, 2020

If v12.15 will be delayed by a week to make space for the security release, is the an opportunity to slide in a fix like nodejs/node#31005 that is a blocker for us from using v12.x in production?

@richardlau
Copy link
Member

@ggoodman It's already in the proposal for 12.15.0 (the release number will be bumped to account for the security release): nodejs/node#31368

@ggoodman
Copy link

ggoodman commented Jan 28, 2020

@richardlau I think what I understand is that v12.15.0 is being delayed by a week so that a security release can come out in the shorter term. I also understand that the linked memory leak fix isn't planned for inclusion in the security release.

What I was asking was whether the team would consider including the memory leak fix in the security release. If that isn't something that makes sense then 👍 but I wanted to make sure I asked. Also, if I've misunderstood, sorry for the confusion.

@richardlau
Copy link
Member

Usually security releases only contain changes related to security issues.

@targos
Copy link
Member Author

targos commented Jan 29, 2020

Ok, so I changed the release date to 2020-02-12.
This is just one week before the next patch release. Should we cancel that one, or delay it by one or two weeks?

/cc @codebytere

@bencripps
Copy link

Any chance we could prioritize the release?

Really hoping to land nodejs/node#31005 which is a blocker for us from using v12.x in production?

@targos
Copy link
Member Author

targos commented Feb 11, 2020

v12.16.0 was released today

@bencripps
Copy link

Awesome, thank you!

@targos
Copy link
Member Author

targos commented Apr 20, 2020

I certainly won't be able to open the proposal for v12.16.3 tomorrow. There are more than 300 commits to audit and many have conflicts.

@targos targos unpinned this issue Oct 23, 2021
@targos
Copy link
Member Author

targos commented Apr 8, 2022

Closing as no more releases are planned.

@targos targos closed this as completed Apr 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests