<div dir="ltr"><div>Hi team!</div><div><br></div><div>So far Photon is largely on
track. As I've previously noted, our estimates for all teams include a deliberate
buffer ("reserve capacity"), to accommodate a broader effort on fixing
performance / Quantum Flow bugs. Since Photon work has stabilized and
things are going well, I'd like to start using this extra capacity to
begin accelerating performance work. But gradually, so we can watch out
for its impact on the rest of Photon.</div><div><br></div><div>To start off, I'd like to ask everyone to take a look at the photon-performance bug tree (<a href="https://bugzilla.mozilla.org/showdependencytree.cgi?id=1363750&hide_resolved=1" target="_blank">https://bugzilla.mozilla.org/<wbr>showdependencytree.cgi?id=<wbr>1363750&hide_resolved=1</a>), and pick one or two bugs to work on over the next couple of weeks. That's it. Let's see how it goes. :)</div><div><br></div><div>A few notes:</div><div><br></div><div>*
That metabug (1363750) in turn tracks a collection of metabugs for
performance in particular areas. I'd suggest finding an area that you're
interested and/or skilled in. There's also metabug 1363777, which
tracks a bunch of random performance work that doesn't cluster into any
particular area.</div><div><br></div><div>* The primary focus is still
on regular Photon work. And, yes, by adding some performance work to
everyone's plates that does mean the regular work will slow down a bit.
We're making use of excess schedule, not asking people to do extra work
on weekends. :-)</div><div><br></div><div>* We built in ~20% reserve
capacity for this work (1 day a week), but we don't need to ramp all the
way to that just yet. If we find that the regular Photon projects need
more time than expected, we'll scale back on performance work to ensure
they're completed.</div><div><br></div><div>* The animation and
onboarding projects started landing code later than anticipated, so I'd
like those teams to hold off on picking up performance work for now. To
the previous point, I want to make sure we have better estimates for
those project areas, to avoid starting performance work only to have to
drop it shortly thereafter.</div><div><br></div><div>Justin<br></div></div>