After a year's worth of development, bug fixes, and integration testing,
we are now ready to enable the latest version [1] of the Safe Browsing
API in Firefox 56, two releases ahead of schedule and only a few weeks
behind Chrome.

We do not expect any user-visible changes, but will be running an
experiment [2] on beta to compare crash rates between the two versions
of the API. After that, the feature will be rolled out to the release
population in stages [3].

I want to take this opportunity to thank Dimi Lee, Henry Chang and
Thomas Nguyen for spending so much time refactoring and eliminating
ancient code (some of it dating back to when Safe Browsing was a Google
extension for Firefox [4] or part of the Google Toolbar [5]). Thanks to
their hard work, we have not only eliminated crashes and fixed
intermittent test failures that have been around for many years, we now
also have a stable codebase and two new module peers [6] with deep
knowledge of this code.

Big thanks to the other Taipei folks who helped make this happen: Ethan
Tseng, Engineering Manager; Wesly Huang, EPM; and Cynthia Tang, QA
Engineer. Without the work of all of these people, we would not have
been able to complete the migration in time for Google's shutdown of the
old servers.

Francois

[1] https://security.googleblog.com/2016/05/evolving-safe-browsing-api.html
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1377267
[3] https://bugzilla.mozilla.org/show_bug.cgi?id=1387651
[4]
https://web.archive.org/web/20051218171531/http://www.google.com/tools/firefox/safebrowsing/index.html
[5]
https://web.archive.org/web/20060412192055/http://tools.google.com/firefox/toolbar/
[6]
https://groups.google.com/d/topic/mozilla.governance/cF9MwHoQ09M/discussion
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to