Release plan - v12.x Current

[BethGriggs]

draft

Week	Approximative date	Release	Releaser
2019 - 17	2019-04-23	v12.0.0	@BethGriggs
2019 - 18	2019-04-29	v12.1.0	@targos
2019 - 19	2019-05-07	v12.2.0	@targos
2019 - 21	2019-05-21	v12.3.0	@BridgeAR
2019 - 21	2019-05-22	v12.3.1	@BridgeAR
2019 - 23	2019-06-04	v12.4.0	@targos
2019 - 25	2019-06-27	v12.5.0	@BridgeAR
2019 - 27	2019-07-03	v12.6.0	@targos
2019 - 30	2019-07-23	v12.7.0	@targos
2019 - 32	2019-08-06	v12.8.0	@BridgeAR
2019 - 33	2019-08-15	v12.8.1 (security)	@targos
2019 - 34	2019-08-20	v12.9.0	@targos
2019 - 35	2019-08-26	v12.9.1	@targos
2019 - 36	2019-09-03	v12.10.0	@BridgeAR
2019 - 39	2019-09-25	v12.11.0	@BridgeAR
2019 - 39	2019-10-01	v12.11.1	@targos
2019 - 41	2019-10-08	v12.12.0	@BridgeAR
2019 - 43	2019-10-21	v12.13.0 (first LTS)	@targos

[targos]

I will probably prepare a new release for next week (as soon as nodejs/node#27379 fixed. This issue breaks one of my server apps and probably many users of create-react-app

[DanielRuf]

I think we can update the README as v12.0.0 was released now =)

https://github.com/nodejs/Release/blob/master/README.md

[DanielRuf]

Also see https://nodejs.org/en/about/releases/

[BridgeAR]

@nodejs/releasers I will be on an airplane on the 18th and thus it would be good if someone else would be able to release the next version. I will update the staging branch and I could also open a release proposal on the 17th. I am just not sure if I get to actually releasing the version on time.

[targos]

@BridgeAR I can push the release tomorrow if you're not there

[targos]

@nodejs/releasers Does one of you have time to prepare a release this week?

[targos]

The schedule is updated. That leaves us with 6 more Current releases before v12.x becomes LTS.

[sam-github]

@BridgeAR are you still planning a 12.x release for today, or this week?

[BridgeAR]

@sam-github I still try to get the proposal out today. I had to bisect issues earlier and that took a while.

[BridgeAR]

@nodejs/releasers we actually skipped last weeks release since no one had time to publish the release. I would be available today and tomorrow to cut a new release instead of next week. That might be favorable, since otherwise there's only one week between the next two releases?

[targos]

SGTM

[BridgeAR]

I updated the release plan accordingly.

[BethGriggs]

Do we expect v12.12.0 (nodejs/node#29919) to be the final planned release of v12.x before it goes LTS? //cc @BridgeAR @targos

[BridgeAR]

@BethGriggs yes, that's the plan as far as I know.

[targos]

That's also what we should do to comply with the LTS policy. If we make another release before LTS, the commits that it contains wouldn't have been baking two weeks in a Current.

[targos]

v12.x Current is over. I think we can close this issue.