On 8/15/2014 2:52 PM, Nils Ohlmeier wrote:
I'm glad we talk about this now :-)
Is there then a way to push the new binary to the CDN, but in an
in-active state (so not all browsers would automatically fetch it) so
that QA's can manually point there browser (or other test framework)
at it?
Cisco can push new binaries to the CDN at any time without affecting
users. Mozilla controls the schedule of OpenH264 updates by linking to
the Cisco CDN from our own update servers, with the
media-gmp-manager.url you mentioned.
The basic sequence for deploying a new OpenH264 version will be to stage
the update on the AUS staging server, run tests against stage, and then
enable the update on the production server.
I think we are also completely missing any automated test around the
download of the plugin. That's what I'm working on right now.
That's great, thank you. Are you doing that testing using the "real"
OpenH264 (which would require the test harness to have access to the
outside internet), or a dummy plugin to basically unit-test the download
mechanism?
What bugs track that test work? I expect that gfritzsche would probably
be the best person to review those tests when they are ready.
--BDS
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media
