Open
Bug 1531492
Opened 6 years ago
Updated 2 years ago
[meta] [socket-process] Define when and how to enable WebRTC networking inside the socket process
Categories
(Core :: WebRTC: Networking, enhancement, P3)
Core
WebRTC: Networking
Tracking
()
NEW
People
(Reporter: drno, Assigned: bwc)
References
(Blocks 1 open bug)
Details
(Keywords: meta)
Currently WebRTC Networking inside the new socket process is controlled via two prefs:
- media.peerconnection.mtransport_process
- network.process.enabled
which both are not set yet (so false).
We need to establish a plan on how and when we are going to flip these prefs to true.
The simplest option is to just flip the prefs in Nightly and let them ride the trains.
Another option is to flip them only in Nightly, but hold them back in Nightly until we have ironed out the fall out bugs from that.
And for Release the question is if we want to do a flip pref shield study instead of just launching it in a given version in the future.
Reporter | ||
Comment 1•6 years ago
|
||
For now we decided to flip the prefs in bug 1531492 and hold the prefs in Nightly only to enable dogfooding and see how many bug reports we will get.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•