00:30:11  * node-ghjoined
00:30:11  * node-ghpart
00:30:18  * node-ghjoined
00:30:18  * node-ghpart
00:30:25  * node-ghjoined
00:30:25  * node-ghpart
00:31:35  * node-ghjoined
00:31:35  * node-ghpart
00:32:06  * node-ghjoined
00:32:06  * node-ghpart
00:34:48  * node-ghjoined
00:34:48  * node-ghpart
00:35:38  * node-ghjoined
00:35:38  * node-ghpart
00:36:28  * 18VAEBU0Zjoined
00:36:28  * 18VAEBU0Zpart
00:36:29  * 7GHAAW6RKjoined
00:36:29  * 7GHAAW6RKpart
01:07:55  * BridgeARquit (Ping timeout: 256 seconds)
01:17:19  * jaywon_joined
01:20:40  * jaywonquit (Ping timeout: 245 seconds)
01:53:10  * jaywon_quit (Remote host closed the connection)
01:53:52  * jaywonjoined
01:58:56  * jaywonquit (Ping timeout: 276 seconds)
02:03:21  * jaywonjoined
02:07:25  * jaywonquit (Remote host closed the connection)
02:07:33  * jaywonjoined
02:07:55  * jaywonquit (Remote host closed the connection)
02:08:21  * jaywonjoined
02:39:43  * jaywonquit (Remote host closed the connection)
02:40:16  * jaywonjoined
03:40:30  <Trott>It looks like GitHub bot is kicking off lite CI jobs automatically-ish? Who set that up?
03:45:02  * jaywonquit (Remote host closed the connection)
04:10:17  * jaywonjoined
05:11:25  <ryzokuken>Trott I guess someone had been talking about that? I'll look up in the source
06:19:49  * jaywonquit (Ping timeout: 265 seconds)
06:22:41  * jaywonjoined
06:25:44  * jaywon_joined
06:29:23  * jaywonquit (Ping timeout: 255 seconds)
06:30:09  * seishunjoined
06:43:32  * node-ghjoined
06:43:33  * node-ghpart
07:02:42  * jaywonjoined
07:06:17  * jaywon_quit (Ping timeout: 255 seconds)
07:30:23  * seishunquit (Ping timeout: 265 seconds)
08:02:25  * jaywonquit (Remote host closed the connection)
08:09:27  * jaywonjoined
08:13:32  * jaywonquit (Ping timeout: 245 seconds)
08:55:08  * BridgeARjoined
09:02:42  * BridgeARquit (Ping timeout: 265 seconds)
09:10:09  * BridgeARjoined
10:25:09  * mylesborinsquit (Quit: farewell for now)
10:25:39  * mylesborinsjoined
11:00:27  * node-ghjoined
11:00:27  * node-ghpart
11:02:27  * node-ghjoined
11:02:27  * node-ghpart
11:19:27  * sxajoined
11:38:47  * jaywonjoined
11:42:51  * jaywonquit (Ping timeout: 240 seconds)
12:05:43  * node-ghjoined
12:05:44  * node-ghpart
12:08:39  * BridgeARquit (Ping timeout: 256 seconds)
13:13:05  * BridgeARjoined
13:25:13  * gabrielschulhofjoined
13:25:22  <gabrielschulhof>Hey, all! When is 10.4.0 coming out?
13:26:04  <gabrielschulhof>I'd like to squeeze https://github.com/nodejs/node/pull/21129 at @MayhemYDG's request: https://github.com/nodejs/node/pull/21129#issuecomment-395021127
13:27:07  <gabrielschulhof>s/squeeze/squeeze in/
13:28:21  <refack>Trott: it was done in https://github.com/nodejs/github-bot/pull/173
13:29:33  <refack>gabrielschulhof: https://github.com/nodejs/node/pull/21167
13:31:06  <gabrielschulhof>refack: Does the two-day wait apply to such realease PRs as well?
13:31:54  <gabrielschulhof>refack: ... because I can land https://github.com/nodejs/node/pull/21129 in about 10 hours.
13:32:21  <refack>I'd say coordinate with mylesborins
13:32:47  <gabrielschulhof>refack: OK.
13:36:41  <refack>gabrielschulhof: on a slightly different subject, give some thought to the idea of merging some of the test addons. I'll talk to you about that later.
13:37:58  <gabrielschulhof>refack: You mean reduce the number of subdirectories under test/addons-napi?
13:38:10  <gabrielschulhof>... and the number of modules that are built?
13:38:33  <refack>Yes. (also if you have opinions on test/addons)
13:39:26  <refack>It becomes a node-gyp load test... just compiling them cn get to 20% of total test time. But now I'm going AFK
13:39:46  <gabrielschulhof>refack: OK.
14:36:40  <mylesborins>gabrielschulhof sorry I wasn't able to get it in
14:36:45  <mylesborins>would have had to delay the release a week
14:37:12  <mylesborins>looks like the website is not updating
14:40:52  <mylesborins>ping rvagg
16:25:02  * seishunjoined
16:26:46  * BridgeARquit (Ping timeout: 264 seconds)
17:04:31  * targosquit (Quit: Connection closed for inactivity)
17:09:54  * juggernaut451joined
17:22:17  <maclover7>mylesborins: is the website still not updating?
17:23:08  <refack>I see 10.4 in the list and as `latest`
17:24:27  <refack>maybe cache, although we had problems with cron tasks - https://github.com/nodejs/build/issues/1314
17:55:27  * node-ghjoined
17:55:27  * node-ghpart
17:57:43  * sxaquit (Ping timeout: 256 seconds)
18:02:27  * seishunquit (Ping timeout: 240 seconds)
18:24:25  * jaywonjoined
18:26:32  * seishunjoined
18:32:53  * seishunquit (Ping timeout: 268 seconds)
18:41:03  * seishunjoined
18:43:37  * gabrielschulhofquit (Ping timeout: 256 seconds)
18:52:58  <mylesborins>the blog post is still not updated
18:53:05  <mylesborins>10.40 release post iss not up
18:53:10  <mylesborins>maclover7 refack rvagg mhdawson_
19:00:20  * node-ghjoined
19:00:21  * node-ghpart
19:01:33  <maclover7>mylesborins: in the nodejs/nodejs.org repo settings page, can you resend the webhook to the webserver
19:01:36  <maclover7>to force it to rebuild the website again
19:01:58  <maclover7>I don't have access to the webhooks for the website repo
19:03:57  * node-ghjoined
19:03:57  * node-ghpart
19:06:47  * Fishrock123joined
19:17:04  * joyeequit
19:17:27  * joyee__joined
19:18:19  * node-ghjoined
19:18:19  * node-ghpart
19:18:45  * joyee__changed nick to joyee
19:18:59  * node-ghjoined
19:18:59  * node-ghpart
19:20:00  * node-ghjoined
19:20:01  * node-ghpart
19:26:51  * node-ghjoined
19:26:51  * node-ghpart
19:42:37  * juggernaut451quit (Remote host closed the connection)
19:42:52  * node-ghjoined
19:42:52  * node-ghpart
20:00:05  <Trott>mylesborins and anyone else: Put a `?` at the end of the URL to bypass caching. I had that problem in Berlin.
20:00:48  * jaywonquit (Remote host closed the connection)
20:02:09  * jaywonjoined
20:02:34  <maclover7>Trott: it looks like the page hasn't been built at all
20:02:37  <maclover7>had tried https://nodejs.org/en/blog/release/v10.4.0/? earlier
20:02:45  * seishunquit (Ping timeout: 245 seconds)
20:02:49  <Trott>Oh well, ignore me. :-P
20:03:14  <maclover7>If you're around, can you resend that webhook
20:03:18  <maclover7>To see if it will build now
20:03:30  <maclover7>Hopefully the server hasn't completely fallen over
20:18:24  * jaywonquit (Remote host closed the connection)
20:18:51  * jaywonjoined
20:20:12  <maclover7>Trott: ^
20:20:31  * node-ghjoined
20:20:31  * node-ghpart
20:21:39  <Trott>maclover7: I've re-added you as an admin to that repo. You can view the webhook at https://github.com/nodejs/nodejs.org/settings/hooks.
20:22:06  * jaywon_joined
20:22:22  * jaywonquit (Read error: Connection reset by peer)
20:23:45  <maclover7>Trott: ok taking a look
20:25:50  <maclover7>Resent webhook, let's see how that works
20:26:19  <maclover7>Trott: mylesborins: can you confirm you can see https://nodejs.org/en/blog/release/v10.4.0/ now
20:35:11  * gabrielschulhofjoined
20:48:29  * seishunjoined
20:59:56  * seishunquit (Ping timeout: 256 seconds)
21:15:23  <mylesborins>I can see you
21:52:12  * node-ghjoined
21:52:12  * node-ghpart
21:52:24  * node-ghjoined
21:52:25  * node-ghpart
21:54:27  * node-ghjoined
21:54:27  * node-ghpart
21:55:19  * node-ghjoined
21:55:19  * node-ghpart
21:55:42  * node-ghjoined
21:55:42  * node-ghpart
21:56:06  * Fishrock123quit (Quit: Leaving...)
21:56:15  * node-ghjoined
21:56:15  * node-ghpart
21:57:19  * node-ghjoined
21:57:20  * node-ghpart
22:04:58  * jaywon_quit (Remote host closed the connection)
22:08:43  * node-ghjoined
22:08:43  * node-ghpart
22:32:30  * BridgeARjoined
23:01:05  * jaywonjoined
23:18:39  * node-ghjoined
23:18:39  * node-ghpart