Firefox/2015/weeklystatus/3-20

Firefox for iOS, v1.0, Risk Profile= At Risk

Why at risk?

Although the team continues to work at a high velocity and the scope has been revised to move less important items to V1.1, or to a sub-list to only address if time allows for the V1.0 release which has cut the list of features not started to just 6, the development time frame is extremely condensed for a v1.0 product. L10N is progressing on a weekly basis. Tracking May 1st as the hard deadline for strings. Team is being mindful of l10n and they are working to get front-end features complete, first to reduce string churn.

Next Steps and Go to Green Plan

1. l10n team has shifted from a monolothic model of translation to an iterative one so strings are translated as they land
2. Team is being very proactive with dogfooding and getting builds out to the testing team quickly and providing rapid responses to bugs and usability issues
3. Although team is being quality orientated, they will stay opportunistic and use every second we have before May12th

Read full Status: https://wiki.mozilla.org/Mobile/Firefox_for_iOS/Status_Report/18-Mar-2015

Firefox for Android, v38.0, Risk Profile = Almost on track

Why?

String freeze declared on time. Feature work has landed except for Send tab which is currently baking on nightly and will be uplifted, soon.

Next Steps

1. Full end-to-end testing with production endpoints for synced Reading List
2. Will monitor fix rate vs. incoming bugs as well as regressions and bouncebacks
3. Healthy balance of the above along with good stability (1.5 crashes or less per 100 ADU) will keep this feature ‘on track’.

Firefox for Desktop, v38.0 - Reading List and Reader View Risk Profile = At risk

Why at risk?

There are three main areas of risk:

1. The readability.js code
2. The reading list sync engine
3. General: condensed schedule and not much time to address issues

Go to green plan

(put update, here)

Firefox for Desktop, v38.0 - Room Sharing for Hello, Risk Profile = On Track

Why?

String freeze declared on time. Tab sharing has been uplifted and the feature is ready for end-to end testing.

Next Steps

1. Stay on top of incoming bugs and issues
2. Will monitor fix rate vs. incoming bugs as well as regressions and bouncebacks
3. Healthy balance of the above along with good stability will keep this feature ‘on track’

Firefox Developer Edition, v40.0, Risk Profile = No risk profile, yet. Ramping up, Fx40 will be Nightly as of 03/30 which will trigger Red/Yellow/Green status

Why?

Code currently on GUM branch; intended scope includes: iOS debugging, enabling the performance tools, and improve firebug.

Next Steps

1. GUM will merge to nightly on 03/30
2. This project will flip to ‘yellow’ post-merge and will be evaluated after 1-2 weeks of Nightly usage; risk profile will then be evaluated based upon code landing and quality