715
edits
(ato's updates) |
(→Minutes: add) |
||
Line 9: | Line 9: | ||
== Minutes == | == Minutes == | ||
=== Work week evaluation === | |||
; ato | |||
: I thought the work week went really well. | |||
: Particularly useful to do the geckodriver 1.0 triage. | |||
: I also thought it useful to discuss CDP and our plan for TPAC. | |||
; whimboo | |||
: It was useful to sit together and talk out issues, and especially that jgraham was also there. | |||
: We only got three days of active work, so next time a full week would be better. | |||
; ato | |||
: We should make a list of bugs we would like to draw attention to during TPAC. | |||
: I believe whimboo has a few issues and I have a few. | |||
; whimboo | |||
: What happens during the meeting? Do we triage the open issue list? | |||
; AutomatedTester | |||
: Yes, if there is time. | |||
; ato | |||
: Despite the fact that it was only three days of active work, I think it was still worthwhile. | |||
: I think we should repeat this. | |||
; AutomatedTester | |||
: Sure. Maybe next year early in February. | |||
=== Web interoperability roadmap === | |||
; AutomatedTester | |||
: I sent out a document about how I think we should do web predictability last week. | |||
: I thought it was good to give other groups an idea what the difference between web interop and web compat is. | |||
: I now need to create a roadmap and I will ask you all for feedback. | |||
: This is part of ensuring we coordinate our work with other teams at Mozilla. | |||
: Hopefully raising our profile. | |||
; ato | |||
: Would this roadmap cover the next quarter, or be in the format of a longer-term vision or plan? | |||
; AutomatedTester | |||
: We need it to be short, medium, and long-term. | |||
: Showing what work would be involved, and how we can hit our goals. | |||
: For example, interoperability reports and getting Firefox engineers to use them. | |||
: If we take on the CDP transport stuff, possibly creating a MVP for getting Puppeteer working. | |||
: Also this about resource allocation. | |||
; ato | |||
: This is a digression, but how do we get RelMan and engineers to understand what the ''important'' web interop issues are? | |||
; AutomatedTester | |||
: I don’t have a clear answer for this, but first getting the reports and then having a discussion about that would make sense. | |||
=== geckodriver 0.23.0 === | |||
; ato | |||
: There are still two outstanding issues. | |||
; whimboo | |||
: We should delay those to 0.24.0, because the regression fixes are more important. | |||
; ato | |||
: Great, I agree. | |||
=== Intermittents update === | |||
; whimboo | |||
: kmag landed a fix for an assertion/crash which caused lots of intermittent failures but this didn't actually helped us | |||
: [(Perma ccov) Assertion failure: m_refCount == 1 or pages_.empty() (Bug 1485985)] | |||
: I don't expect much to change this week. Still waiting for Kris to have a look at this bug | |||
: [[needs investigation by jim] Firefox startup hang for ASAN builds on Linux64 (Bug 1487243)] | |||
: This is caused by getting a dbus connection during startup; The hanging code is about to get moved away from startup and put closer to the dbus requiring code. | |||
: We might even see that fixed today! | |||
== Status updates == | == Status updates == |
edits