Bi-Weekly Status Report for mus+ash 6/18

17 views

Skip to first unread message

Daniel Xie

unread,

Jun 21, 2018, 1:51:14 PM6/21/18

to musta...@chromium.org, graphi...@chromium.org, services-dev

Hi all,

The mus+ash team will start sending out updates on a ~2 week cadence to give you insight on what the team is working on. These are some of the highlights for the next 2 weeks:

Q3 Planning
The team is currently finalizing Q3/18 OKR planning. Some highlights are:
Migrate --mash to OopAsh
Complete implementation of Window Service 2 (WS2)
Use WS2 for ChromeOS Browser
Refactor Ash headers from Browser

KeyboardShorcutViewer as a standalone app (841020)
The team is making great progress from refactoring Keyboard Shortcut Viewer to run as a standalone app using the Window Service. This is enabled on trunk, and we are aiming to ship this feature in M69. QA handoff should happen shortly (ETA week of 6/25).

Windows Service 2 (aka WS2)
We are in the process of adding a feature that enables Ash, when running out of process, to run the WindowService on its main thread. This config will be known as OopAsh. OopAsh and --mash will converge soon. We hope to complete this in the next two to four weeks.

Browser on WS2
Once --mash has been converted to --OopAsh, the team will focus on refactoring Browser UI to use the WindowService. The plan is to enable this while Ash and the Browser are in the same process. This is a necessary step before we can separate Ash and the Browser. Browser code will use DesktopNativeWidgetAura (similar to desktop Chrome), while Ash will use NativeWidgetAura (as it always has). The first milestone is to scope the work items needed for this project in Q3.

Ash Refactoring
Good progress made on ash refactoring. As of 6/20, we are down to 309 ash includes in Browser with test includes (vs 342 5/30). Not including tests, we are at 134 ash includes in Browser (vs 151 5/30). Browser_tests with mash enabled pass rate is at 90% (vs 90% 5/30).