Changes

Jump to: navigation, search

Media/WebRTC

467 bytes removed, 16:48, 30 September 2017
Updated triage guidelines
*[https://wiki.mozilla.org/Media/WebRTC/ReleaseNotes/53 Firefox 53 WebRTC & Web Audio Release Notes]
*[https://wiki.mozilla.org/Media/WebRTC/ReleaseNotes/54 Firefox 54 WebRTC & Web Audio Release Notes]
 ==Product Backlog==Go to *[https://wiki.mozilla.org/Media/Bugs#WebRTC_Bugzilla_Queries WebRTC bugs/ReleaseNotes/55 Firefox 55 WebRTC & Web Audio Release Notes] to search for all open WebRTC bugs (including untriaged and unconfirmed bugs).
===Triage Guidelines===
The Product Backlog is continually maintained to ensure relative priorities are understood. Individual priority may vary based circumstance.
* Priorities follow the Firefox Desktop Standard:
** Priority 1 - Blocker, must-fix before shipping. Almost by definition of P1, the "affected" flags and "tracking" flags for the bug should be set when it's triaged. ** Priority 2 - Major impact, considering severity × probability. Not a blocker for shipping.High priority backlog (bugs we are currently working on or will be working on next)** Priority 3 - Average Bug. definitely a problem, but doesn't stop someone from using the product. Lower priority backlog ** Priority 4 - Minor or polish bugs that are real issues (especially in aggregate) and annoying.Bugs we will accept patches for** Priority 5 - Low-impact. something Parking lot (Bugs we'd fix, but mostly only bothers the discerning user. Little impact do not plan to spend any time on usability.)
*RANK: As priority buckets start to have a large amount of bugs in them, the The Rank field can be used to call attention to higher or lower rank and provide lets us prioritize bugs within a way to sort easily priority bucket (P2, P3, etc) in bugzilla. To have some rhyme/reason to the order - Rank should relate to Priority. The "Ranking" number does not need to be unique. Unless there is a reason to for a bug to be considered before (or after) others in the Priority bucket - the triager will default to mid-range value.** P1 Rank options=10-199, default 155** P2 Rank options=2010-2919, default 2515** P3 Rank options=3020-3929, default 3525** P4 Rank options=4030-4939, default 4535** P5 Rank options=5040-5949, default 5545** any valid * Note: P5 and "parking-lot"-labelled bugs that we don't believe we'll ever put resources on, but would accept patches for, go in are treated identically. We no longer use "parking-lot" area; it is a legacy classification.
<p> </p>
*The Blocking-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
**"-" means QE should not look at
***Typically QE-verify"-" goes with "in-testsuite" being set to "+", to show testing via another method.
*"Points" should be set when known (if nothing set - assumed a "1" or very small). Most relevant if taking a bigger bug so we know when bugs are large bits of work.
===Filing a bug===
Confirm
654
edits

Navigation menu