Media/WebRTC/2013-01-03

From MozillaWiki
< Media‎ | WebRTC
Jump to: navigation, search

1/3/2013, 9am Pacific

  • FF20 uplift is *Monday*. Land code Sunday or earlier!

Notes:

1) Interop with Google: where are we?

  • We have patch sets for FF and Chrome. FF patches are mostly known/simple issues. Chrome patches are more complex
  • Still has issues to resolve. Video doesn't always work in FF->Chrome direction
  • Still needs a server to do some SDP/etc translation
    • Ekr needs to write this stuff down
    • Need test page
  • doesn't work behind all nats yet - may be us, may be chrome, may be the combo
  • Delay issue to investigate
  • Maire: This is really awesome! Will work to make this a joint announcement

2) gUM blocker bugs: where are we?

  • gum UI: Open questions on strings and icons -- (Bugs 798336, 799417) & Bug 802656
  • Bug 825594 (pref on gum) has dependencies now

3) Blockers for the rest of WebRTC (PeerConnection, DataChannels): where are we?

  • What is blocking us from pref'ing these on?
  • Bug 796463 (pref on webrtc) has dependencies now
  • Should pref-on rely on both patches to 825785 or just what has already been pushed? Answer: it'd be good to have both.

4) Android work/status

5) Discuss any current problems for people or issues that haven't been discussed -- or Any Heads up for the group

  • Adam has been having trouble reproducing Bug 821884 and Bug 825480, though recently he could reproduce Bug 825480 when downloading the latest Nightly so he is digging in further.

6) Testing

  • Read the etherpad - jsmith is out due to needing to buckle down on b2g work
  • [jsmith] Barrier - Back from PTO, but locked into b2g work until Jan 15th
  • [jsmith] Gum automation is almost fully landed with one last issue to be fixed
  • [jsmith] Doing overall much better in the leak arena
  • [jsmith] Functional issues with the WebRTC full stack flow definitely needs more digging now that we're killing off major crashers and sec bugs - already pulled out 5 - 6 bugs from quick exploratory testing
  • [whimboo] Automation bug triage has been a heavy focus - making sure bugs are on file for issues caught on automation and tracking it
  • [whimboo] Tried and failed to get crashtests landed on central due to bug discovered during landing

_________________

For Reference:

Interop (Firefox-Chrome) blockers: https://bugzilla.mozilla.org/buglist.cgi?list_id=5124656;resolution=---;status_whiteboard_type=allwordssubstr;query_format=advanced;status_whiteboard=blocking-webrtc-interop

Blocker list for gUM: https://bugzilla.mozilla.org/buglist.cgi?query_based_on=gum%20blocking;status_whiteboard_type=anywordssubstr;query_format=advanced;status_whiteboard=blocking-gum%2B;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;known_name=gum%20blocking

Blocker List for preffing PeerConnection and DataChannels (the rest of WebRTC) on: https://bugzilla.mozilla.org/buglist.cgi?query_based_on=WebRTC%20blocking;status_whiteboard_type=anywordssubstr;query_format=advanced;status_whiteboard=blocking-webrtc%2B;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;known_name=WebRTC%20blocking

Combined Blocker List for all of WebRTC (gUM, PeerConnection, DataChannels): https://bugzilla.mozilla.org/buglist.cgi?list_id=5234368;query_based_on=WebRTC%2Fgum%20blocking;status_whiteboard_type=anywordssubstr;query_format=advanced;status_whiteboard=blocking-webrtc%2B%20blocking-gum%2B;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;known_name=WebRTC%2Fgum%20blocking

Retrieved from "https://wiki.mozilla.org/index.php?title=Media/WebRTC/2013-01-03&oldid=496964"