02:50:49  * targosquit (Quit: Connection closed for inactivity)
05:45:55  * node-slack-botpart
05:46:07  * node-slack-botjoined
08:42:49  * targosjoined
11:16:04  * sxajoined
11:39:19  * node-ghjoined
11:39:20  * node-ghpart
13:38:16  * lucalanzianiquit (Ping timeout: 246 seconds)
13:53:38  * lucalanzianijoined
14:08:11  * node-ghjoined
14:08:11  * node-ghpart
14:09:33  * node-ghjoined
14:09:33  * node-ghpart
14:10:26  * node-ghjoined
14:10:26  * node-ghpart
14:12:36  * node-ghjoined
14:12:36  * node-ghpart
14:13:36  * node-ghjoined
14:13:36  * node-ghpart
14:14:23  * node-ghjoined
14:14:23  * node-ghpart
14:21:12  * node-ghjoined
14:21:12  * node-ghpart
14:24:52  * node-ghjoined
14:24:52  * node-ghpart
14:48:50  * node-ghjoined
14:48:50  * node-ghpart
15:28:33  * node-ghjoined
15:28:33  * node-ghpart
15:32:32  * node-ghjoined
15:32:32  * node-ghpart
15:34:43  * node-ghjoined
15:34:43  * node-ghpart
16:09:33  <ljharb>now that https://github.com/nodejs/node/pull/25234 has landed, what would it take to get a patch release of v11 out?
16:25:31  <node-slack-bot>[bethanygriggs] We have a v11 release plan here https://github.com/nodejs/Release/issues/397 - looks like there is one due 8th Jan
16:33:07  <ljharb>that sounds fine as long as it’s a patch; it’d be great not to leave a minor behind with the wrong version of npm
17:28:33  * node-ghjoined
17:28:33  * node-ghpart
18:24:46  * node-ghjoined
18:24:46  * node-ghpart
18:27:44  * node-ghjoined
18:27:44  * node-ghpart