Closed Bug 1651235 Opened 4 years ago Closed 4 years ago

Enable WebRTC usage of socket process on early beta and earlier

Categories

(Core :: Networking, enhancement, P2)

enhancement

Tracking

()

VERIFIED FIXED
mozilla80
Tracking Status
firefox80 --- verified

People

(Reporter: mjf, Assigned: mjf)

References

Details

Attachments

(1 file)

We're ready to enable webrtc on the socket process in early beta and earlier (rather than just nightly).

Assignee: nobody → mfroman
Severity: -- → S3
Priority: -- → P2
Summary: e → Enable socket process on early beta and early
Summary: Enable socket process on early beta and early → Enable socket process on early beta and earlier
Pushed by mfroman@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/42aa9267e077
enable webrtc usage of socket process on early beta and earlier. r=drno
Summary: Enable socket process on early beta and earlier → Enable WebRTC usage of socket process on early beta and earlier
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla80

Comment on attachment 9162016 [details]
Bug 1651235 - enable webrtc usage of socket process on early beta and earlier. r?drno!

Beta/Release Uplift Approval Request

  • User impact if declined: This is to allow QE to qualify the socket process sandbox in Beta.
  • Is this code covered by automated tests?: Yes
  • Has the fix been verified in Nightly?: Yes
  • Needs manual test from QE?: Yes
  • If yes, steps to reproduce: This is general sandbox qualifications for webrtc using the socket process. QE should follow the same process used to qualify the socket process sandbox in Nightly.
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): This is only a pref change to enable webrtc usage of the socket process in early beta. It has been used in Nightly for quite some time now.
  • String changes made/needed:
Attachment #9162016 - Flags: approval-mozilla-beta?
Flags: qe-verify+

We only have one early beta build left this cycle - is this really worth taking on Beta79 at this point vs. letting it ride to Beta80 naturally instead?

Flags: needinfo?(mfroman)

That is up to Haik and/or Nils more than me.

Flags: needinfo?(mfroman)
Flags: needinfo?(haftandilian)
Flags: needinfo?(drno)

Nils is driving the enabling of the socket process so I'll let him respond on this.

Flags: needinfo?(haftandilian)

As QA managed to test the feature in 79 by manually flipping thee pref we do have green lights to use it in 79. So I don't think that we need the uplift any more.

Flags: needinfo?(drno)

Comment on attachment 9162016 [details]
Bug 1651235 - enable webrtc usage of socket process on early beta and earlier. r?drno!

Thanks everyone.

Attachment #9162016 - Flags: approval-mozilla-beta? → approval-mozilla-beta-
QA Whiteboard: [qa-triaged]

Verified as fixed, the feature webrtc on the socket process is enabled (by default: “network.process.enabled” =true and “media.peerconnection.mtransport_process” =true) on early beta: Beta 80.0b1 - Beta 80.0b5 and Nightly 81 or earlier and disabled starting with Beta 80.0b6.

Status: RESOLVED → VERIFIED
QA Whiteboard: [qa-triaged]
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: