Firefox OS/Comms/Dialer/Sprint/v2.1-S7/20141016-StandupNotes

From MozillaWiki
< Firefox OS‎ | Comms‎ | Dialer‎ | Sprint‎ | v2.1-S7
Jump to: navigation, search

Blockers

  • 2.1+ bug 1081714 - [Dialer][Call Screen] Phone number & name disappear from the call screen after making several calls sequentially
    • Assigned to Alexandre.
    • He has a fix that involves bug 1083729.
  • 2.1+ bug 1081854 - GAIA follow-up to bug 978639 (for GCF case 31.4.2.1.3)
    • Assigned to Tamara.
    • Depends on bug 978639, which is scheduled to be landed on 10/17.
    • We estimated that this will take 3 days, so it should land by 10/22.
  • 2.1+ bug 1074379 - Dialer does not always show incoming call # and prevents the user to answer
    • Assigned to Alexandre.
    • He has a fix that involves bug 1083729.
  • 2.1? bug 1083729 - Workaround for the callscreen leaking
  • 2.1- bug 1082876 - TypeError: context is null at: app://callscreen.gaiamobile.org/gaia_build_defer_index.js line: 84
    • Assigned to Gabriele.
    • In reality is basically a blocker, since it’s blocking a partner’s testing, even if there are no STR.
    • Cause unknown, possibly something in shared/js/dialer/tone_player.js
  • 2.1+ bug 1082139 - JavascriptException: JavascriptException: TypeError: window.getComputedStyle(...) is null at: app://callscreen.gaiamobile.org/gaia_build_defer_index.js line: 146
    • Assigned to Germán.
    • Info requested from Anshul.
    • It could be related to bug 548397 - window.getComputedStyle() returns null inside an iframe with display: none
  • 2.1? bug 1075699 - Calling voicemail by long-pressing the 1 button displays an error and then calls
    • Assigned to Tamara.
    • Should lose blocker status.
    • Ready to land a fix, but waiting for vendor to reply to a needinfo.
  • 2.2? bug 1081745 - [Dialer] "cancel" is not translated for multiple languages
    • Assigned to Germán.
    • Looks like an easy fix.
  • 2.2? bug 1081348 - [Dialer][Ringtone] Ringtone only plays once, does not loop, when receiving a call and will not ring on subsequent calls.
    • Unassigned.
    • Caused by bug 994190, so we need Ben Turner to investigate it.

drs

  • Admin:
    • Nothing new.
  • Next steps:
    • MVC proposal.
    • Reviews.
  • Patches:
    • None yesterday.
  • Reviews:
    • bug 977588 - [Dialer] The Active call screen does not have the option to place calls on hold.
      • r?
    • bug 1068093 - Remove legacy transition code from the callscreen
      • r-, new r?
    • bug 1069835 - [ partner confidential ]
      • r?
    • bug 1081028 - [Dialer] Though CDMA Network doesn't support single call hold, but user can hold single call via BT Headset
      • r?
    • bug 1079794 - [Dialer] [Callscreen] When you are in active call and other call is entering you can't hold and answer with headset button
      • r-
    • bug 1083500 - Dialer needs to notify user when it can't make a call due to a problem with cardState
      • r-
    • bug 977056 - [Dialer] Visual discrepancies: Call ended view under conference call participants list
      • r-
  • Other:
    • Met with Wilfred and the other comms apps owners to talk about 2.2 features.
    • In a discussion with a guy from Intel about the Telephony API.
    • Did some of the action items from the retrospective and other meetings.

gtorodelvalle

  • Admin:
    • Jorge told me he was under some pressure in his new group and asked me to consider assigning the 3 bugs he was currently working on to other people:
      • bug 943389 - [Dialer][Conference call] Detailed contact info on conference call on group line is missing
      • bug 1029313 - [Dialer][DSDS] With 2 SIMs; The matching result disappears after typing in the last correct digit when dialing
      • bug 1062799 - Call information is not updated on the fly after creating a contact
    • Unless we consider them prioritary enough, maybe we could move them to the next sprint.
  • Next steps:
    • bug 9770056: [Dialer] Visual discrepancies: Call ended view under conference call participants list
      • I started the compilation of a new build including the patches Hsin-Yi mentioned that could solve the issue regarding having 2 “connected” (mozTelephonyCall.state) calls at the same time. It is taking ages and slowing my machine down a lot :( I’ll test it as soon as I have the new build.
    • bug 977588 - [Dialer] The Active call screen does not have the option to place calls on hold.
      • Helping Paco with this bug.
    • bug 1082139 - JavascriptException: JavascriptException: TypeError: window.getComputedStyle(...) is null at: app://callscreen.gaiamobile.org/gaia_build_defer_index.js line: 146
    • After investigating the issue, it seems that it could be related to “bug 548397 - window.getComputedStyle() returns null inside an iframe with display: none” and a bad configuration of the tests which are causing the issue.

thills

    • bug 1075699 - T-Mobile Voicemail Bug. Still no reply from partner (emailed y’day) on the NI. Still listed as a blocking status.
    • bug 1079143 - BlueTooth Bug - This is being listed as critical to fix now (even though we unassigned it). I’m going to look at this today and see if the 2second delay can possibly fix this because they are looking for an uplift. Need to talk about this in scrum.
    • bug 1068093 - Removed legacy call screen transitions - Posted up new changes to this.
    • bug 1081854 - Waiting on RIL patch
    • bug 1083402 - “X has left the call does not show up”. Etienne and Carrie confirm this is a regression. Do we need to prioritize this?

jlorenzo

Manual test run status for Dialer: Total: 348 => http://mzl.la/fxos-dialer-2-1-moztrap-active-test-cases Passed: 336 Failed: 8 => http://mzl.la/fxos-dialer-2-1-moztrap-test-run-3-non-passed Invalidated: 1 => http://mzl.la/fxos-dialer-2-1-moztrap-test-run-3-non-passed Not done: 1 => https://moztrap.mozilla.org/manage/case/13733/