Firefox/Metro/WorkWeekII: Difference between revisions

Line 116: Line 116:
***  We should peek into metrics to get win8 ADI's on nightly(~20,000) ,aurora(<20,000) & beta(~95,000) to see if we are targeting the needed user population and have a strategy around uplift's.
***  We should peek into metrics to get win8 ADI's on nightly(~20,000) ,aurora(<20,000) & beta(~95,000) to see if we are targeting the needed user population and have a strategy around uplift's.
***  Do our updates work fine? We should do a round of update testing on different win8 configurations . We never want to leave user's stranded an old build.
***  Do our updates work fine? We should do a round of update testing on different win8 configurations . We never want to leave user's stranded an old build.
**** QA request, include round of update testing during the merge week when we uplift
***  L10n - How many locales are we planning on supporting ? Do we have a cut-off on this for launch?
***  L10n - How many locales are we planning on supporting ? Do we have a cut-off on this for launch?
***  Stability - Given the limited population on nightly it is hard to get attention or track any new crashers.  But once we move up the trains this will change. So we will need more Engineering/QA attention to help resolve these (https://crash-stats.mozilla.com/products/MetroFirefox)
***  Stability - Given the limited population on nightly it is hard to get attention or track any new crashers.  But once we move up the trains this will change. So we will need more Engineering/QA attention to help resolve these (https://crash-stats.mozilla.com/products/MetroFirefox)
Confirmed users
976

edits