Hey folks, I figured it was time for another email.
We're down to 1 tracking bug, and it's not ours. We have a large set of supported locales, a plan for going global, our own reliable crash reporting, and our UX (particularly top sites) and perf are looking great. We're in good shape for a v1. Emily, Steph, and the rest of the team are continuing to dig into Bug 1194726. This is a system bug, not one of ours, and we've tried two workarounds so far. If we can't find a fix we'll submit an RC anyway; we're just making good use of the time until marketing and legal gives the all-clear on the screenshots and App Store text. After that we will be in a little bit of a period of limbo between submission and acceptance or rejection, development-wise. Our priority if we're rejected will be to fix anything that caused rejection, but otherwise, we want to start crunching through things that missed v1. Stefan and myself will (tomorrow morning?) do a quick blitz through our current 1.1+ and 2.0+ tracking bugs, spitting out pluses and noms. What was 2.0 is now 1.1, and what was 1.1 is now 1.0.*, so we're aiming to reuse + for things we'll ship ASAP and 1.1+ for things targeted at November. Our goal is to get stuff in the + list so the team has a clear idea of what to work on in the short term. Tuesday's triage will address the new noms, continue the Aha card work that we started today, and set the stage for some straightforward scoping/estimation/breakdown work. The expectation is that + items will be included in RC2 if we need it, so at the moment, for the sake of simplicity, I do not expect us to branch. We'll branch (to a v1 branch off master; see earlier emails) when we have a submission accepted. 1.0.* work will occur on that branch, and 1.1 November work, including Swift 2.0 conversion, will happen on master. Stefan et al, please flesh out anything I missed. I'll close this mail by sending my huge thanks to everyone for their herculean efforts in getting this from a pivot at the end of last year through to this week, with RC builds of a beautiful, fast browser. As always, our l10n and a11y contributors deserve huge gratitude for dealing with our changing schedule and usual ignorance, but my particular thanks this week go to Robin and Darrin, who I know are ridiculously overworked but still turned everything around with care and speed, and our dev team, who have remained wonderful human beings while uncomplainingly shouldering huge loads. Thanks to everyone, too, for putting up with Triage Richard®. You're the best. -R
_______________________________________________ mobile-firefox-dev mailing list mobile-firefox-dev@mozilla.org https://mail.mozilla.org/listinfo/mobile-firefox-dev
