Firefox OS/Comms/Dialer/Sprint/v2.1-S5/20140929-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 Tamara. Looks like this is related to bug 927862.
• 2.1? bug 1073534 - "cancel" is a non-localizable string in the audio output picker
  • Landed a fix.

drs

• Admin:
  • Nothing new.
• Next steps:
  • bug 1068109 - Restore 2s delay before callscreen is closed
    • Have to review this for Tamara.
  • bug 1061398 - Incall keypad layout needs adjustment
    • Gave feedback-. Have to give feedback today for Paco.
  • bug 1070808 - [ secure/hidden ]
    • Have to review this for Tzu-Lin.
  • bug 1060451 - Refactor copied-and-pasted displayMessage() code in emergency-call/dialer.js taken from dialer/telephony_helper.js
    • In progress. I expect to have a patch today.
  • bug 1070993 - Entering or scrolling in call log sometimes shows empty list
    • Kats doesn't have a device for this, so I will investigate if I have time.
• Done:
  • Did pre-sprint and sprint planning.
  • bug 1069286 - No tactile feedback when dialling a number
    • Review+ for Anthony.
  • bug 1062799 - Call information is not updated on the fly after creating a contact
    • Review- for Jorge.
  • bug 1061398 - Incall keypad layout needs adjustment
    • Feedback+ for Paco.
  • bug 1045820 - Port SimPicker implementation in MSAB and comms apps to GaiaSimPicker
    • Waiting for Anthony, Francisco to review
  • bug 1073534 - "cancel" is a non-localizable string in the audio output picker
    • Landed 2 patches for master and v2.1.

thills

• bug 1024341 - Wakeup the device after call hangs up
  • We split this into several bugs. Right now, I'm working on one of the child bugs of this.
• bug 1068109 to restore the 2s delay before the call screen goes away.
  • Finished off incorporating changes for the patch from last review & submitted.
• bug 1070066 - [Dialer] The call screen does not display call info and shows a black background after repeatedly placing calls
  • qdot is looking at this from settings perspective and there are some ideas floating around there, qa is requested, but wanted to discuss what next steps should be on this one as it's masked by 1068109, but not sure what we should do to move this forward.

Rik

• Absent/no report

gtorodelvalle

• Absent/no report

pacorampas

• Absent/no report

jpruden92

• Absent/no report