Plan for Node.js 11 Current releases

[targos]

Week	Approximative date	Release	Releaser
2018 - 49	2018-12-07	v11.4.0	@BridgeAR
2018 - 51	2018-12-18	v11.5.0	@BethGriggs
2018 - 52	2018-12-26	v11.6.0	@MylesBorins
2019 - 03	2019-01-18	v11.7.0	@BridgeAR
2019 - 04	2019-01-24	v11.8.0	@MylesBorins
2019 - 05	2019-01-30	v11.9.0	@targos
2019 - 07	2019-02-14	v11.10.0	@targos
2019 - 09	2019-02-28	v11.10.1	@rvagg
2019 - 10	2019-03-05	v11.11.0	@BridgeAR
2019 - 11	2019-03-14	v11.12.0	@BridgeAR
2019 - 13	2019-03-28	v11.13.0	@targos
2019 - 15	2019-04-11	v11.14.0	@BethGriggs
2019 - 16	2019-04-30	v11.x.y	@codebytere

/cc @nodejs/releasers

I propose this plan for the next Node.js 11 Current releases, until the week before Node.js 12 is supposed to be released.
It's a simple rule: one release every two weeks, with an exception of three weeks during end of year holidays. I always put Tuesday as approximative date but the release could happen any day of the week, depending on releaser's availability.
We already have a volunteer to do the next release. @BethGriggs is week 51 OK for you?

[MylesBorins]

I'd personally be more comfortable with the releases happening on Tuesday... Would you be open to making that change?

…

On Sat, Dec 8, 2018, 9:52 AM Michaël Zasso ***@***.*** wrote: Week Approximative date Releaser 2018 - 51 2018-12-19 @BethGriggs <https://github.com/BethGriggs> 2019 - 02 2019-01-09 ??? 2019 - 04 2019-01-23 ??? 2019 - 06 2019-02-06 ??? 2019 - 08 2019-02-20 ??? 2019 - 10 2019-03-06 ??? 2019 - 12 2019-03-20 ??? 2019 - 14 2019-04-03 ??? 2019 - 16 2019-04-17 ??? /cc @nodejs/releasers <https://github.com/orgs/nodejs/teams/releasers> I propose this plan for the next Node.js 11 Current releases, until the week before Node.js 12 is supposed to be released. It's a simple rule: one release every two weeks, with an exception of three weeks during end of year holidays. I always put Wednesday as approximative date but the release could happen any day of the week, depending on releaser's availability. We already have a volunteer <#395> to do the next release. @BethGriggs <https://github.com/BethGriggs> is week 51 OK for you? — You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub <#397>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAecV6va8riTLov0wMZDusJaY-nHgYj0ks5u29IngaJpZM4ZJq0p> .

[targos]

@MylesBorins OK, I changed the dates... But those should not be considered fixed. I personally have more time to do releases on Wednesdays or Thursdays.

[BridgeAR]

I suggest to use the dates as recommendation and let the releasing person be flexible with the actual day while trying to prevent releases on Fridays.

I am fine to volunteer for e.g., each even 11 release. That way I know when to take some time for it.

[MylesBorins]

@BridgeAR I generally push for releases on Tuesday for 2 reasons

1. Give external teams appropriate time during the week to adopt the new release
2. Give us a large buffer in case of release problems. We have had releases that broke stuff, it wasn't pointed out until wednesday / thursday, we then in turn still had time to respond and get a new release out during the week without requiring a firedrill during the weekend.

I personally have more time to do releases on Wednesdays or Thursdays.

While I totally understand the timing issue here, my hope would be that the majority of release work has been done in advance, a least multiple days in advance. So, for example, a release can be prepared and proposed on a Thursday so that testing can begin. This was the only work to be done on tuesday is promotion... which "shouldn't" take more than an hour.

[targos]

I volunteer for 2019-01-22

[targos]

Ping @nodejs/releasers do we have a volunteer for this week? It would be nice to have a patch release with npm 6.5.0 stable.

[BridgeAR]

I'll prepare the release tomorrow.

[ljharb]

how goes today's patch release? :-D

[BridgeAR]

@ljharb currently there are lots of conflicts between master and 11.x and I did not get to resolve all of these and I have to get some sleep but I'll try to finish it tomorrow.

It's likely that we should backport a couple of older commits first though. Otherwise each release is going to become more complicated.

[ljharb]

I'm most interested in seeing nodejs/node#25234 make it into an 11.6 patch release; as long as it doesn't get delayed to an 11.7, i'm more than happy to wait til you have time :-) Thanks!

[MylesBorins]

@ljharb that one is already on staging 🎉

…

On Tue, Jan 8, 2019, 8:05 PM Jordan Harband ***@***.*** wrote: I'm most interested in seeing nodejs/node#25234 <nodejs/node#25234> make it into an 11.6 patch release; as long as it doesn't get delayed to an 11.7, i'm more than happy to wait til you have time :-) Thanks! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#397 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAecV1hT21uU_361beeclh63oaa8pzP1ks5vBUBGgaJpZM4ZJq0p> .

[MylesBorins]

@BridgeAR are you still able to do this?