Open Bug 818631 (webrtc_updates) Opened 9 years ago Updated 1 year ago

[meta] Update WebRTC code from WebRTC.org stable branches

Categories

(Core :: WebRTC, defect, P3)

defect

Tracking

()

People

(Reporter: jesup, Unassigned)

References

(Depends on 1 open bug, Blocks 3 open bugs)

Details

(Keywords: leave-open, meta)

Periodically we should update media/webrtc/trunk from the current (or new) stable branch of WebRTC.org code.

For FF18 and FF19, we used the 3.12 branch also used by Chrome 23.

For FF20, we'll likely use the 3.19 branch (currently to-be-created).

Mark bugs to be checked for resolution by an update here (also so we know what to back out of our tree if it's fixed upstream) by adding them to the dependency list here. ('webrtc_updates')

I'll note updates here as well.
Blocks: 818618
Blocks: 814699
Keywords: meta
Whiteboard: [leave-open] → [leave-open] [WebRTC] [blocking-webrtc-]
Blocks: 828917
Depends on: 830247
3.12 landed in bug 797671.
Depends on: 797671
Blocks: 830908
Blocks: 833733
Blocks: 838799
Blocks: 779110
Blocks: 800508
Blocks: 897981
Blocks: 899159
No longer blocks: 899159
Blocks: 943353
Blocks: 995884
No longer blocks: 818618
Depends on: 1250356
Whiteboard: [leave-open] [WebRTC] [blocking-webrtc-] → [leave-open]
Depends on: 1198458
Depends on: 1109248
Depends on: 987979
Depends on: 880879
Depends on: 901583
Depends on: 932112
V57 is landing in bug 1341285
Depends on: 1341285
Summary: Update WebRTC code from WebRTC.org stable branches → [meta] Update WebRTC code from WebRTC.org stable branches
Assignee: rjesup → dminor
Depends on: 1376873
Keywords: leave-open
Whiteboard: [leave-open]
No longer blocks: webrtc_upstream_bugs
Depends on: 1492214
Depends on: 1439997
Depends on: 1515699
Blocks: 1525393

Can we update now, since 1492214 is closed?

(In reply to David Heidelberg from comment #3)

Can we update now, since 1492214 is closed?

We'll be planning and prioritizing work at our all-hands in mid-June, so I'll know better at that point when we plan to update again. Based upon past experience, it will take 6 to 9 months for the update to land once work begins.

Is there anything in particular you are looking for? We do sometimes backport specific features outside of doing a update.

(In reply to Dan Minor [:dminor] from comment #4)

(In reply to David Heidelberg from comment #3)

Can we update now, since 1492214 is closed?

We'll be planning and prioritizing work at our all-hands in mid-June, so I'll know better at that point when we plan to update again. Based upon past experience, it will take 6 to 9 months for the update to land once work begins.

Is there anything in particular you are looking for? We do sometimes backport specific features outside of doing a update.

compatibility with libvpx 1.8.0 - since now it's impossible to build firefox with system libvpx 1.8.0 .
Is there anything I can do to help with this being possible?

Blocks: 1430779
Blocks: 1566976
Depends on: 1607238
No longer blocks: 1525393
Depends on: 1654112
Assignee: dminor → nobody
Severity: normal → S3
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.