Media/WebRTC/2013-02-26

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

Tuesday, Feb 26, 2013, 9am Pacific:

Note:

1) gUM blockers for release: where are we? All are tracking-firefox20.

  • We talked about these a lot on Friday. So I'd like to focus on PeerConnection,DataChannel blockers.

Note - Anything that is deemed as blocking-gum+ for Fx20 needs to be nominated for tracking-firefox20, so that these bugs end up on release management's radar.

2) PeerConnection, DataChannels blocking-webrtc+ bugs

  • Progress on figuring out what's going on with Intermittent oranges
    • abr has added a bunch of logging (thank you!)
    • What can we do about the DISPATCH_SYNC issue?
  • Standard8's intermittent bug when he starts/stops video quickly (Bug 835283)
  • Security safety & userful reporting from Aurora
    • Adding optimized/production assertions
  • Hook up DataChannels to the SDP (Bug 837035)
  • Specifying STUN server by DNS name (Bug 843644 and Bug 837919)
  • One crash test where we leak the world (Bug 841930)
  • Audio latency (Bug 785584)

3) Security bugs and how we address them

  • We're preffed on now - we need to be more careful how we follow the rules for dealing with security bugs. We've had slack given our code was mostly off-by-default. This is no longer the case.
  • We can land security fixes without sec-approval if it's a recent regression on m-c (with fair or total certainty, such that we feel safe marking Aurora as "unaffected"). Most of our fixes right now do NOT fall into this bucket.
    • Security bugs that affect Aurora should be nominated for uplift as soon as possible.
  • Note that most non-null-deref crashers and most thread-safety issues (and all use-after-frees) are going to be sec-critical.
    • sec-criticals are tracked closely by security-group, and we have a goal as an organization of dealing with sec-criticals within 2 weeks if at all possible, preferably less.
    • Please give security bugs priority in most cases, or if you defer working on them make sure it's a limited deferral.
    • Some sec bugs may not have enough information to address immediately. If possible, find some way to get that information via retest, added debugs/asserts, etc.
  • We need to make security-critical assertions (especially threading ones) active in production builds for now. You can key off MOZ_WEBRTC_ASSERT_ALWAYS (see bug 843695)

4) Android development/MWC feedback

  • Demos seem to be going well
  • gcp was able to land code that fixed the 90 degree rotation problem
  • Many thanks to everyone on the team for all their hard work

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

  • Team in Taiwan working on FirefoxOS
  • [jsmith] End-User Dogfooding strategy within Mozilla - First Steps

6) Testing

  • [whimboo] Whimboo on point for Test Framework Refactoring Part 3
  • [whimboo] Also has some data channel mochitests in his local queue
  • [jsmith] WebRTC MWC Testing last week
  • [jsmith] Some getUserMedia signoff testing last week
  • [jsmith] Finish off signoff testing for getUserMedia
  • [jsmith] Working on test plan specs for PC and Data Channels for more formal testing
  • [jsmith] Working on test app to learn and experiment with the PC and Data Channel APIs

_________________

For Reference

Blocker list for gUM release: 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 releasing PeerConnection and DataChannels (the rest of WebRTC): 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) release: 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 Android User Stories/Progress: https://webrtc-apps.etherpad.mozilla.org/4

Retrieved from "https://wiki.mozilla.org/index.php?title=Media/WebRTC/2013-02-26&oldid=535813"