Firefox OS/Comms/Dialer/Sprint/v2.1-S6/20141006-StandupNotes

Blockers

• 2.1+ bug 1070066 - [Dialer] The call screen does not display call info and shows a black background after repeatedly placing calls
  • Assigned to Doug. Kyle M (:qDot) is looking into the platform side. He says he found a fix (see bug 1076597), but there's a new IDB error, and we need Ben Turner for that (who is on vacation).
  • I'm going to try fixing this by ensuring that there are no stale callscreen app instances in the main process. Kyle H suggested a method to do this.
• 2.1+ bug 1074379 - Dialer does not always show incoming call #
  • Assigned to Anthony.
  • This appears to be related to bug 1070066.
  • There's no clear fix yet, but Olli is on this partially.
• 2.1+ bug 1068109 - Restore 2s delay before callscreen is closed
  • Assigned to Tamara. Recently got blocker status.
  • Ready to land.
• 2.1+ bug 1075699 - Calling voicemail by long-pressing the 1 button displays an error and then calls
  • Assigned to Tamara. Can only be repro'd on a T-Mobile SIM.
• 2.0+ bug 1074601 - The SIM 2 Voice mail displayed as a "Unknown contact" in dialer view and call log view
  • Assigned to Tzu-Lin, being reviewed by Doug. This is under control.
• 2.0? bug 1066874 - [Dialer] User can be put into a state where there is no one on the other line in a phone call and user is unable to end call
  • Unassigned, new nom. Looks like it could be bad, and is not a regression.

drs

• Admin:
  • We are beginning to really fall behind on blockers. We must redouble our efforts to get everything done by Friday.
  • We also have the additional objective of completing our sprint bugs by the end of the week, which is looking unlikely to happen now.
• Next steps:
  • bug 1070066 - [Dialer] The call screen does not display call info and shows a black background after repeatedly placing calls
    • I will take a stab at fixing this within Gaia. I'm not sure how likely it is for us to get a fix from Kyle before Friday.
  • bug 1066874 - [Dialer] User can be put into a state where there is no one on the other line in a phone call and user is unable to end call
    • I will likely take this and investigate.
• My patches:
  • bug 1060451 - Refactor copied-and-pasted displayMessage() code in emergency-call/dialer.js taken from dialer/telephony_helper.js
    • Landed.
  • bug 1076231 - [SimPicker] fix racy unit tests
    • Landed.
• Reviews:
  • bug 1061398 - Incall keypad layout needs adjustment
    • r+, landed
  • bug 1062799 - Call information is not updated on the fly after creating a contact
    • r-
  • bug 831974 - [B2G][Dialer] User has to press 1 for a long time before Voicemail is reached
    • r-
  • bug 1068109 - Restore 2s delay before callscreen is closed
    • r+, ready to land
• Other:
  • bug 1067883 - [ partner confidential ]
    • Provided info, split this off into other bugs.
      • bug 1077073 - Display an error when putting a call on hold fails
      • bug 1077075 - Augment telephony API to notify client code of errors when attempting hold(), resume(), etc.
  • bug 1075726 - Calling voicemail by long-pressing the 1 button (and then hanging up) leaves the dialer with "123" pre-entered (and possibly with a contact preselected for autodialing)
    • Was able to repro this after setting the voicemail number to "123".