[13:34:59] mdholloway: o/ do you want to have a quick hangout about saved pages / offline reading? [13:35:33] dbrant: sure, one sec [13:38:36] dbrant: ok, omw [15:37:55] phuedx: on the way? [15:50:19] niedzielski: mdholloway: bearND: how do we feel about a re-release of Beta today? (to fix the plurals crash) [15:51:13] dbrant: fine with me [15:54:03] +1 [15:57:42] dbrant: are we waiting on any other patches? [15:58:16] niedzielski: don't believe so! [16:01:35] sounds good to me [16:02:40] maxbinder: spretro? [16:14:47] dbrant: er, so we don't need this connectivity patch? [16:39:18] bearND: i'm thinking of doing an mcs deployment during the window in ~20 minutes to see if the latest patches eliminate the wiktionary 404s. any objection? [16:39:59] niedzielski: oops sorry; if you think the connectivity patch is g2g, then go for it [16:40:19] dbrant: just trying to test it out right now [16:42:32] on that patch, i should probably revert to what was in PS1. PS2 introduces changes that need discussion. [17:06:11] bmansurov: i am trying to be a big man on campus and attend the web standerp but no one is here. has it been cancelled? [17:06:29] niedzielski: sorry, we're at a different place [17:06:41] https://hangouts.google.com/hangouts/_/wikimedia.org/web-retro?authuser=0 [17:06:50] niedzielski: not sure if you can join [17:07:03] bmansurov: ok, i'll just catch it another time [17:07:06] thanks! [17:07:09] niedzielski: tomorrow! [17:11:39] bearND: does https://gerrit.wikimedia.org/r/#/c/299709 look ok to you? i'm thinking of doing a deployment and that would be a nice bug fix to get in [17:12:59] mdholloway: i'm looking at it right now. I may need to test it a bit more. Also not sure why you're not reusing the date formatting function. [17:13:12] something with hyphenDelimited [17:14:35] bearND: oh, that's because all of our dateUtil date formatting functions take a Request object as the input [17:14:45] which is probably a good thing [17:14:59] mdholloway: k [17:15:02] didn't want to make them complex just for this one special case [17:15:09] i could write a separate function for it, though [17:22:06] mdholloway: sorry for the delay. This patch needs a manual rebase [17:22:18] bearND: that's ok! doing now [17:56:07] dbrant bearND mdholloway: just kind of waiting on the test results from google. release notes are up for your review [17:57:00] niedzielski: from google? what test is that? [17:57:14] dbrant: the prelaunch report. it just came in [17:57:35] oh, i don't think i've seen those yet! [17:58:01] dbrant: oh, well it's under the prelaunch report tab of the production app (it comes in after i upload the alpha) [17:58:38] very cool [17:58:49] dbrant: it's kind of new. we had enabled it a few releases back [17:59:14] dbrant: i'm not sure it's likely to catch a bug but it's still kind of nice [17:59:38] free additional testing = can't hurt [18:01:58] dr0ptp4kt: i'm not sure how this escaped my attention until now, but our 1:1 this afternoon conflicts with an android team mtg with design to discuss navigation over haul options [18:02:27] s/over haul/overhaul [18:17:00] niedzielski-afk: release notes lgtm [18:44:03] does anyone know if there's an easy way to see mediawiki extension usage stats for a given lang wiki - i.e. how many enwiki pages are use imagemap extension? [18:47:15] niedzielski-afk: release notes look good to me [19:24:44] hey jdlrobson. question for when you have time. In general, is it true that the browser should support lazy loading and "we" should not worry about it? [19:25:11] I'm asking since it's not clear for me by looking at the literature, for example, why we don't provide an extension for Chrome/Firefox. [19:25:18] instead of lazy loading on site, jdlrobson. [20:34:55] hey leila [20:35:19] there's an argument yes [20:35:30] but 1) for many end users browser extensions are an enigma [20:36:11] 2) there's a case to be made that you wouldnt want to lazy load images on a website like flickr.com but you would on Wikipedia - so it can be inconvenient [20:36:39] but yes if browsers supported this by default there would be less of a motivation to do what we are doing [20:36:55] I see. thanks jdlrobson. :) [20:37:16] leila: i owe you some replies to talk page on Japanese wiki [20:37:30] re (2), ideally the browser should differentiate between different websites based on the content they serve and does a customized lazy loading. [20:37:37] the short answer though is I did those super quickly just to get a rough idea. I need to redo them. [20:37:52] I thought dr0ptp4kt owes me that jdlrobson. So in my accounts, you're good. ;) [20:37:56] Better to look at Adam's more detailed analysis on Bengali/Farsi [20:38:11] (I'm going over the analysis now, so np jdlrobson) [20:50:46] niedzielski: release notes lg2m, but see my note in Play Store notes [20:52:17] dbrant: resolved: fixed [20:58:02] dbrant: i recommend we skip tsg testing for this release since it's so similar to 148 [20:58:25] niedzielski: yep, my thoughts as well. [21:01:33] dbrant: what Play Store notes were you referring to? [21:02:10] bearND: I asked Stephen to add line #39 in the etherpad [21:03:13] dbrant: ah, ok. And that one goes to the Play Store release notes. Thanks [21:06:59] dbrant: niedzielski: bearND: looking at the failing authentication tests, i see the underlying issue but i think the failure will just go away when we stop supporting legacy login/createaccount flows. i'm pretty sure authmanager is here to stay; anyone object to my taking out the legacy code? [21:08:16] mdholloway: sounds good to me. i think there's a phab for it. i was thinking it would be easier to fix by first ripping out the old code [21:08:37] T137504 [21:08:37] T137504: [Dev] Remove old AuthManager code - https://phabricator.wikimedia.org/T137504 [21:09:00] note: we'll still be failing periodic tests due to needing jdk 8 set up on integration-slave-trusty-1023 but i'm hoping hashar can help us out with that in the next little while [21:09:51] thanks, dbrant and stashbot! [21:12:32] niedzielski: yeah, that makes sense. i saw you mentioned that and it sounded about right and i'm even more convinced of it after a little digging. :) [21:15:13] mdholloway: yeah I have seen your task [21:15:30] mdholloway: I am busy with other things tomorrow. IF that goes well I will look at the jdk8 issue [21:15:42] unless someone else looks at it [21:16:18] hashar: o/ yeah, i am not worried. whenever you have time. i guess there's also a question of maybe moving the job to a jessie machine. anyway, i'll look forward to chatting about it when you (or someone) gets time [21:16:22] mdholloway: I dont think we have jdk8 on Trusty, so we would probably want to move to a Jessie slave [21:16:34] and set it up as the slave-trusty-1023