Confirm
1,094
edits
Changes
updated
==Contacts and Useful Links==
*[https://wiki.mozilla.org/Webrtc/contacts Contacts for webRTC]
*[https://wiki.mozilla.org/LoopWebrtc/wiki links Useful Links for webRTC]
* [https://mozilla.github.io/webrtc-landing/gum_test.html Click here] to test webRTC features in the Firefox browser
*[https://wiki.mozilla.org/RapidRelease/Calendar Firefox Release Calendar]
===Firefox 40===
<p> </p>
<bugzilla>
{
"component":["WebRTC","WebRTC:%20Networking","WebRTC:%20Signaling","WebRTC:%20Audio/Video"],
"bug_status":"RESOLVED",
"include_fields":"id, summary, status, assigned_to",
"target_milestone":"mozilla40"
}
</bugzilla>
<p> </p>
===Firefox 39===
<p> </p>
<p> </p>
'''Product Backlog'''
* [http://mzl.la/1BCZXck Bugzilla Ranked "Firefox-backlogwebRTC+" listtagged bugs]
**Add the "Rank" Column to your results and sort on Rank
***The option to "Change columns" is at bottom of search results
**Search is based on "Flagsbacklog" - "does not contains the string" - firefox-backlog"webrtc+"
* [http://mzl.la/1BD0meY Un-triaged or firefox-backlog- bugs]
<p> </p>
*The FirefoxBlocking-backlog flag is used to Flag called "Backlog" track bugs that are approved or not for the Backlog ("webRTC+" , "parking lot")
*QE-Verify is a flag that developers should be setting. QE uses to filter which bugs they check.
**"+" means that QE should look at the bug and it can be verified with human eyes
*[[Media/WebRTC/2012-04-19| Meeting Notes from Thu, Apr 19, 2012]]
*TRELLO
** [https://trello.com/b/weRHRo0X/loop-33-sprint-2-7-7 Loop Sprint work]
