Platform/2012-10-23: Difference between revisions
< Platform
Jump to navigation
Jump to search
Jprosevear (talk | contribs) No edit summary |
Jprosevear (talk | contribs) |
||
| Line 65: | Line 65: | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
| <big>0.0</big> | | <big>0.0%</big> | ||
| <big>0.0</big> | | <big>0.0 days</big> | ||
| <big>0.0</big> | | <big>0.0 days</big> | ||
| <big>0</big> | | <big>0 bugs</big> | ||
| <big>0</big> | | <big>0 bugs</big> | ||
|- | |- | ||
! scope="row" | <small> | ! scope="row" | <small>Patches Reviewed within 1 Week</small> | ||
! scope="row" | <small>SG:Crit Resolution Time</small> | ! scope="row" | <small>SG:Crit Resolution Time</small> | ||
! scope="row" | <small>Top Crash Resolution Time</small> | ! scope="row" | <small>Top Crash Resolution Time</small> | ||
| Line 77: | Line 77: | ||
! scope="row" | <small>Unresolved Beta Trackers</small> | ! scope="row" | <small>Unresolved Beta Trackers</small> | ||
|} | |} | ||
* Patches Reviewed within 1 Week | |||
** Percentage of patch reviews initiated within the last 3 months that were completed within 1 week | |||
** There is a long tail of very old reviews that impacts this number very negatively if we include all open reviews preceding the previous 3 months | |||
* SG:Crit Resolution Time | |||
** Time from when a bug is tagged as sg:critical to when it is marked RESOLVED/FIXED | |||
** It seems as though that bugs can take a long time to be tagged as sg:critical however | |||
* Top Crash Resolution Time | |||
** Time from when a bug is tagged as topcrash to when it is marked RESOLVED/FIXED | |||
** It seems as though that bugs can take a long time to be tagged as topcrash however | |||
==Key Issues== | ==Key Issues== | ||
==Roundtable== | ==Roundtable== | ||
Revision as of 18:40, 22 October 2012
« previous week | index | next week »
Platform Meeting Details
- Tuesday 2012-10-23 - 11:00 am Pacific
- Dial-in: Audio-only conference# 95312
- People with Mozilla phones or softphones please dial x4000 Conf# 95312
- US/Toll-free: +1 800 707 2533, (pin 4000) Conf# 95312
- US/California/Mountain View: +1 650 903 0800, x4000 Conf# 95312
- US/California/San Francisco: +1 415 762 5700, x4000 Conf# 95312
- US/Oregon/Portland: +1 971 544 8000, x4000 Conf# 95312
- CA/British Columbia/Vancouver: +1 778 785 1540, x4000 Conf# 95312
- CA/Ontario/Toronto: +1 416 848 3114, x4000 Conf# 95312
- UK/London: +44 (0)207 855 3000, x4000 Conf# 95312
- FR/Paris: +33 1 84 88 37 37, x4000 Conf# 95312
- Gmail Chat (requires Flash and the Google Talk plugin): paste +1 650 903 0800 into the Gmail Chat box that doesn't look like it accepts phone numbers
- SkypeOut is free if you use the 800 number
- Warp Core Vidyo Room / SFO-Boardroom
- join irc.mozilla.org #planning for back channel
Products/Projects
Firefox OS
Firefox Desktop
Firefox Mobile
Metro [Weekly]
Stability Report [Weekly]
Mobile
Nightly :
- bug 803289 - java.lang.NullPointerException: at org.mozilla.gecko.BrowserApp.onPrepareOptionsMenu(BrowserApp.java)
Not as much concern for other channels at this moment:
- recently landed in nightly:
- bug 782508 - Enable use of hardware H.264/AAC/MP3 decoders in Android libstagefright omx plugin for ICS/JB
Aurora:
Beta:
Release :
B2G
- UI for crashes on b2g needed still
- Margaret helping out with crash ui
- symbols still needed for crash reports to get meaningful stacks on socorro
- ADU still needed to understand crash rates on socorro
Snappy [Weekly]
Games [1st Tuesday of Month]
Mobile Web Compat [2nd Tuesday of Month]
Critsmash [3rd Tuesday of Month]
Memshrink [4th Tuesday of Month]
Engineering Metrics
| 0.0% | 0.0 days | 0.0 days | 0 bugs | 0 bugs |
| Patches Reviewed within 1 Week | SG:Crit Resolution Time | Top Crash Resolution Time | Unresolved Aurora Trackers | Unresolved Beta Trackers |
|---|
- Patches Reviewed within 1 Week
- Percentage of patch reviews initiated within the last 3 months that were completed within 1 week
- There is a long tail of very old reviews that impacts this number very negatively if we include all open reviews preceding the previous 3 months
- SG:Crit Resolution Time
- Time from when a bug is tagged as sg:critical to when it is marked RESOLVED/FIXED
- It seems as though that bugs can take a long time to be tagged as sg:critical however
- Top Crash Resolution Time
- Time from when a bug is tagged as topcrash to when it is marked RESOLVED/FIXED
- It seems as though that bugs can take a long time to be tagged as topcrash however