Closed Bug 1916480 Opened 5 months ago Closed 5 months ago

Fx129 DRM video playback action items

Categories

(Release Management :: Retrospectives, task)

Product:
Release Management
Component:
Retrospectives
Platform:
x86_64
macOS
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: dmeehan, Assigned: jimm)

References

Details

As discussed in the Fx129 retro, the following are action items to follow-up on for the Hulu incident:

  1. The window of time between the bug report, triage, and investigation
  • Anything we could improve here to speed this up? We quickly had a fix once the bug was investigated.
  1. Testing coverage of Hulu; assess Hulu testing outside of the US (Only available by default in US and Japan)
  • Anything we could improve here to catch this earlier in Nightly/Beta? The bug was reported during RC week for Fx129

:jimm please move and/or split this bug to the relevant Product/Component. It was created to track an action item from the Fx129 retro.

Assignee: dmeehan → jmathies
Flags: needinfo?(jmathies)

Tracy and I met after he had a meeting with QA on this, so he can fill in the details on what steps we're taking within that team. Generally we spoke about:

  1. While hulu testing was covered in Nightly and Beta pre-release testing, this bug was not identified. QA team is aware of this and is assessing how that happened, and what steps we can take to mitigate that in the future.

  2. We identified a better process for bug filing. The original bug was filed by default as an S3, which was a mistake. In the future these bugs (based on the best judgement of the QA team) should:

  • not have a default severity assigned so that they fall into the team's regular triage process.
  • potentially be marked as tracking:? if they seem serious, so that REOs pick them up and can follow up on them.

One other note I would add that I thought of after I spoke with Tracy -

  • require regression ranges vs. guessing what release the regression occurred in would have helped. The bug was misidentified as a long standing issues vs. a fresh regression, which threw engineering off on the severity.
Flags: needinfo?(jmathies) → needinfo?(twalker)

Thanks Jim. We're working to ensure this won't be repeated. Also we're going to try your suggestion for filing non-high severity bugs, by not setting severity, so they'll end up in Engineering triage, as well as setting tracking if an issue seems serious. We'll err on the side of caution to make sure issues get notices sooner. We'll disseminate this decision to the QA team next week.

Flags: needinfo?(twalker)

Thanks to you both for the info here.
It doesn't look like this needs to track anything else or be moved to a different Product/Component.

Status: NEW → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.