Engineering Effectiveness Newsletter (July 2022 Edition)

Welcome to the July edition of the Engineering Effectiveness Newsletter! The Engineering Effectiveness org makes it easy to develop, test and release Mozilla software at scale. See below for some highlights, then read on for more detailed info!


Detailed Project Updates

Bugzilla and Bugbug

  • Suhaib implemented several new features for autonag!
  • dkl implemented changes to the See Also field in Bugzilla which will now take any properly formatted URL in addition to local bug IDs.
  • To reduce spam in Bugzilla, users without “editbugs” can no longer make changes to bugs in the Graveyard classification (ie. bugs associated with archived products).

CI and Treeherder

Crash Management

Lint, Static Analysis and Code Coverage

OS Integration and Security


Release Engineering and Management

  • Starting with Firefox 103, the Release Management team are releasing a planned dot release 2 weeks after the previous release go-live.
  • Fx-Trains now offers a calendar view of upcoming releases
  • gbrown reviewed and fixed openh264 builds and signing, and added notarization of openh264 on Mac.
  • Guided by :RyanVM, :jcristau and :jlorenzo improved the automation around our Android products. Starting with Gecko 104:
    • Android-Components gets released off of instead of Github Releases
    • Fenix/Focus are not immediately shipped anymore. We now have a 2-step process where builds are promoted and sent to our testing population before shipping them to Github or
    • Version numbers now follow the gecko scheme. This means 104.0.0-beta.1 is now called 104.0b1.
    • L10n bumps and Android-Components bumps are now automatically approved and merged if they passed CI, on the release branches. This used to work on the main branches only.


Thanks for reading and see you next month!