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](https://github.com/nodejs/Release/issues/395) to do the next release. @BethGriggs is week 51 OK for you?