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!
Highlights

   -

   Autonag received many new features, including auto-rotating triage owners
   <https://github.com/mozilla/relman-auto-nag/pull/1512>,
highlighting inactive
   reviewers <https://github.com/mozilla/relman-auto-nag/pull/1531> or fuzzing
   problems <https://github.com/mozilla/relman-auto-nag/pull/1564> and  less
   bugmail spam <https://github.com/mozilla/relman-auto-nag/pull/1565>!
   -

   A promising fix <https://bugzilla.mozilla.org/show_bug.cgi?id=1716727>
   has landed which appears to reduce Windows OOM crashes by as much as 20%!
   -

   Most of Firefox’s test tasks have been migrated from AWS to GCP
   <https://bugzilla.mozilla.org/show_bug.cgi?id=1577276>, resulting in a
   large cost savings!
   -

   Many improvements landed to the Code Review bot, including hints if an
   issue may not be an author’s fault
   <https://github.com/mozilla/code-review/pull/1243>, colorized output
   <https://github.com/mozilla/code-review/pull/1223>, a fix for warnings
   <https://github.com/mozilla/code-review/pull/1224> and less noise
   <https://github.com/mozilla/code-review/pull/1236>!

Detailed Project UpdatesBugzilla and Bugbug

   -

   Suhaib implemented several new features for autonag!
   -

      Ability to automatically update the triage owner
      <https://github.com/mozilla/relman-auto-nag/pull/1512> on Bugzilla
      based on a rotation calendar.
      -

      Highlight patches
      <https://github.com/mozilla/relman-auto-nag/pull/1531> that are
      waiting for review from inactive or unavailable reviewers.
      -

      Ability to perform actions without triggering bugmail
      <https://github.com/mozilla/relman-auto-nag/pull/1565>! This will
      reduce noise when the bot is performing actions that do not require
      attention.
      -

      Bring attention to bugs that cause issues for fuzzing
      <https://github.com/mozilla/relman-auto-nag/pull/1564>.
      -

   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

   -

   ahal, jlorenzo and others released Taskgraph 2.0
   <https://pypi.org/project/taskcluster-taskgraph/2.0.0/>! See the migration
   page
   
<https://taskcluster-taskgraph.readthedocs.io/en/latest/reference/migrations.html#x-2-x>
   for tips on how to upgrade from 1.x
   -

   ahal revamped Taskgraph’s documentation
   <https://taskcluster-taskgraph.readthedocs.io/en/latest/> by writing new
   content, porting content from Firefox Source Docs, and giving it a nicer
   theme.
   -

   masterwayz migrated most of Gecko’s test tasks
   <https://bugzilla.mozilla.org/show_bug.cgi?id=1577276> from AWS to GCP.
   -

   Valentin performed a major Django 4.0 upgrade in Treeherder.

Crash Management

   -

   Alexandre Lissy made Linux system symbol scrapers run automatically on
   TaskCluster <https://bugzilla.mozilla.org/show_bug.cgi?id=1777423>.
   Symbols and unwinding information for Firefox builds packaged by major
   Linux distributions as well as Firefox dependencies will now be
   automatically scraped every 24h.
   -

   Alexandre Lissy added a task that reprocesses crashes that were missing
   system symbols <https://bugzilla.mozilla.org/show_bug.cgi?id=1779245>
   after we scraped new ones, thus ensuring that all crash reports are
   properly symbolicated, even after the fact. This works on all platforms for
   which we have working scrapers (Windows and Linux currently).

Lint, Static Analysis and Code Coverage

   -

   Many great improvements landed in the Code Review bot!
   -

      vrigal added a hint <https://github.com/mozilla/code-review/pull/1243>
      if the issue comes from a parent revision.
      -

      EvaBardou ensured the bot will no longer post previously found issues
      <https://github.com/mozilla/code-review/pull/1236> on newer
      Phabricator revisions.
      -

      EvaBardou fixed a bug in the backend
      <https://github.com/mozilla/code-review/pull/1224> preventing
      warnings from being displayed.
      -

      EvaBardou colorized the bot’s comments
      <https://github.com/mozilla/code-review/pull/1223> according to their
      meaning.

OS Integration and Security

   -

   The Windows Spotlight team continues to take a targeted approach to
   addressing high-impact issues for our Windows users. Main areas of focus in
   July were:
   -

      Multi-monitor issues
      
<https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=substring&list_id=15997335&status_whiteboard=%5Bwin%3Amultimonitors&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&classification=Other&j_top=OR&resolution=---&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED>
      -

      Fullscreen issues
      
<https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard=%5Bwin%3Afullscreen&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&query_format=advanced&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&classification=Other&resolution=---&status_whiteboard_type=substring&j_top=OR&list_id=15997323>
      -

      Various sizing/DPI issues
      
<https://bugzilla.mozilla.org/buglist.cgi?resolution=---&j_top=OR&status_whiteboard=%5Bwin%3Asizing&status_whiteboard_type=substring&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&classification=Other&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&list_id=16057752>
      -

      Stability (crashes, hangs)
      
<https://bugzilla.mozilla.org/buglist.cgi?list_id=15997327&status_whiteboard_type=substring&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&classification=Other&status_whiteboard=%5Bwin%3Astability&j_top=OR&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&query_format=advanced&resolution=--->
      -

   OOM crashes have been identified as a source of anywhere between 30-50%
   of crashes on Windows. rkraesig, in coordination with the broader Windows
   Spotlight team, has taken a deep-dive into possible remediations, with one
   particularly promising approach
   <https://bugzilla.mozilla.org/show_bug.cgi?id=1716727> having the
   potential of reducing these OOM crashes by as much as 20%. We are now
   awaiting the numbers to evaluate the actual effectiveness of this fix.
   -

   bobowen has landed a change to use the WER Runtime Exception module
   <https://bugzilla.mozilla.org/show_bug.cgi?id=1682520> which allows us
   to catch crashes that occur earlier in startup than ever before!
   -

   Looking forward, the Windows Spotlight team will also start
addressing high-impact
   issues affecting touch devices
   
<https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=substring&list_id=15997330&status_whiteboard=%5Bwin%3Atouch&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&classification=Other&j_top=OR&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&query_format=advanced&resolution=--->
   .

PDF.js

   -

   calixte made accessibility improvements
   <https://github.com/mozilla/pdf.js/pull/15110> and added touch support
   
<https://github.com/mozilla/pdf.js/commit/71db08a139c379f0b56cd057422e8624db860c0c>
   to PDF editing!

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
   <https://fx-trains.herokuapp.com/calendar/> 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
      https://shipit.mozilla-releng.net/ 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 archive.mozilla.org.
      -

      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.

Other

   -

   ahal added a new :searchfox: role to firefox-source-docs
   
<https://searchfox.org/mozilla-central/rev/4a15041348e08fb0d6f5726015c32861e663fbfe/python/mozbuild/mozbuild/sphinx.py#198>
   which can be used to more conveniently link to Searchfox.


Thanks for reading and see you next month!

-- 
You received this message because you are subscribed to the Google Groups 
"[email protected]" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CAAJAz%2B6RhMcEmZM9nAK1GMLRm7Y4BUCNJE8kTuEM51%2Bqo55gww%40mail.gmail.com.

Reply via email to