On Fri, Aug 15, 2014 at 12:16 PM, Benjamin Smedberg <[email protected]> wrote:
> > 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. > > Yes, the filenames on the CDN are unique so nothing is ever overwritten. There are also no plans currently to ever delete anything from it. This means that it's up to the Firefox update process to specify which version to use. That can be changed at any time after they are up on the CDN. I assume then that you would want to insert some QA process in between when we add to the CDN and when the update info is changed. -EH _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
