Confirmed users
14,525
edits
Releases/Firefox 23/Test Plan: Difference between revisions
→Mitigating Strategy
| Line 1,674: | Line 1,674: | ||
* [softvision] roll up failed/unclear Moztrap tests into the "Firefox N Testing" emails so we can fix broken tests | * [softvision] roll up failed/unclear Moztrap tests into the "Firefox N Testing" emails so we can fix broken tests | ||
* [ashughes] raise discussion about running a weekly QA post-mortem (modeled from RelEng's meetings) | * [ashughes] raise discussion about running a weekly QA post-mortem (modeled from RelEng's meetings) | ||
=== All-hands Post-mortem === | |||
==== Discussion ==== | |||
* is generating build2 for RC worth it? | |||
* need a single source of truth for features | |||
* should we make Beta 10 RC1, offer it to Beta users, to get more stability soak time? | |||
* relationship building between QA, Dev, and other teams | |||
==== Actions ==== | |||
* joduinn to investigate desktop repack - channel changing | |||
* bsmedberg to run his script on build#1 crash data | |||
** if we can find it, then we'll continue making build #2 automatically | |||
** if we can't find it, then we'll stop making build #2 and make more dot releases :( | |||
** ''result'': found no crashes with build1 so we need to discuss dropping build2 from our standard process; this will mean potentially doing more .1 releases and some weekend work; a risk and trade-off we are willing to make I think based on prevalence | |||
* lsblakk to create meeting about RC instead of beta 10 | |||
** QA supports this; stop doing Beta 10 and offer Beta/RC users the same RC1 build; grants us a couple more days of soak time for stability | |||
* lsblakk to speak to Laura about finding out about putting in a tab for users about a specific change - timing, finding out sooner - what causes/guidelines about when to do this | |||
* lsblakk - check with Axel if having a hook on l10n repos for key/visible string would help protect localization teams from errors like [fr] tools in the future; especially for string changes | |||
* akeybl to start a discussion about a single source of truth for feature tracking; potentially reuse wiki portal for bug queries (ie. relnote flagged bugs, feature keyworded bugs, tracking bugs, etc) | |||
=== Meeting Details === | === Meeting Details === | ||