Update WebRTC code to webrtc.org stable branch 64

ASSIGNED
Assigned to

Status

()

P2
major
Rank:
15
ASSIGNED
a year ago
13 days ago

People

(Reporter: dminor, Assigned: dminor)

Tracking

(Depends on: 3 bugs, Blocks: 7 bugs)

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

a year ago
61 hasn't branched yet, but that will be our target for the next webrtc.org update.
(Assignee)

Updated

a year ago
Blocks: 818631
Rank: 15

Updated

a year ago
Blocks: 1347070
Depends on: 1390217
(Assignee)

Updated

a year ago
Depends on: 1391257

Updated

a year ago
Blocks: 1391319
(Assignee)

Updated

a year ago
Depends on: 1336429
Mass change P1->P2 to align with new Mozilla triage process
Priority: P1 → P2
Note: if https://bugs.chromium.org/p/webrtc/issues/detail?id=8536 isn't in webrtc.org 61, and it's applicable (I think it may well be), we'll want to cherry-pick the patch that landed upstream to fix an H264 packet-loss-recovery bug
(Assignee)

Comment 3

8 months ago
I think we should target 64 for the next update. That entered beta on Dec. 18th.
Summary: Update WebRTC code to webrtc.org stable branch 61 → Update WebRTC code to webrtc.org stable branch 64
(Assignee)

Updated

7 months ago
Status: NEW → ASSIGNED
(Assignee)

Updated

6 months ago
Blocks: 1439997
Depends on: 1451394

Updated

3 months ago
Blocks: 1395259

Updated

3 months ago
Blocks: 1462125
(Assignee)

Updated

13 days ago
Depends on: 1480090
You need to log in before you can comment on or make changes to this bug.