Confirmed users
1,798
edits
Releases/Post-mortems/Firefox 16.0: Difference between revisions
Jump to navigation
Jump to search
Releases/Post-mortems/Firefox 16.0 (view source)
Revision as of 16:56, 30 October 2012
, 30 October 2012no edit summary
(→QA) |
No edit summary |
||
| Line 3: | Line 3: | ||
* Mozilla Mountain View: Very Good Very Mighty, 3V | * Mozilla Mountain View: Very Good Very Mighty, 3V | ||
* Vidyo Room: Release Coordination | * Vidyo Room: Release Coordination | ||
== Other communication channels == | == Other communication channels == | ||
* irc.mozilla.org #planning for back channel | * irc.mozilla.org #planning for back channel | ||
* [https://etherpad.mozilla.org/16-0-Post-Mortem This etherpad] for real-time notes (we'll copy the wiki page in at the beginning of the meeting, and out at the end) | * [https://etherpad.mozilla.org/16-0-Post-Mortem This etherpad] for real-time notes (we'll copy the wiki page in at the beginning of the meeting, and out at the end) | ||
== Talking Points == | == Talking Points == | ||
=== Timeline === | === Timeline === | ||
| Line 15: | Line 13: | ||
* Released, throttled due to Patch Tuesday, 10/9 | * Released, throttled due to Patch Tuesday, 10/9 | ||
* Pulled off the wire and from download pages on the morning of 10/10 | * Pulled off the wire and from download pages on the morning of 10/10 | ||
====16.0.1==== | ====16.0.1==== | ||
* Found out about the necessity for a 16.0.1 morning of 10/10 ({{bug|720619}}) | * Found out about the necessity for a 16.0.1 morning of 10/10 ({{bug|720619}}) | ||
| Line 22: | Line 19: | ||
* Released morning of 10/11, unthrottled | * Released morning of 10/11, unthrottled | ||
* Throttled for feedback on 10/13 | * Throttled for feedback on 10/13 | ||
====16.0.2==== | ====16.0.2==== | ||
* Starting discussing the necessity for a 16.0.2 on 10/18 | * Starting discussing the necessity for a 16.0.2 on 10/18 | ||
| Line 29: | Line 25: | ||
* Went to build on 10/24 | * Went to build on 10/24 | ||
* Released on 10/26, unthrottled | * Released on 10/26, unthrottled | ||
=== Release Issues === | === Release Issues === | ||
* {{bug|799348}} – [Firefox 16] load event is not always triggered by XUL windows | * {{bug|799348}} – [Firefox 16] load event is not always triggered by XUL windows | ||
| Line 35: | Line 30: | ||
* {{bug|786740}} – CSS transition with rounded borders cause rendering issues | * {{bug|786740}} – CSS transition with rounded borders cause rendering issues | ||
** web regression, but didn't have major user impact | ** web regression, but didn't have major user impact | ||
=== QA === | === QA === | ||
* [Action from 15.0] - QA (ashughes) to add checks for no what's new page to Beta 1 update testing and to release update testing | * [Action from 15.0] - QA (ashughes) to add checks for no what's new page to Beta 1 update testing and to release update testing | ||
** This was done as of 16.0b1 -- manual spotcheck in place until we have an automated test | ** This was done as of 16.0b1 -- manual spotcheck in place until we have an automated test | ||
* QA sign-off wasn't clear for 16.0.2, prevented a push to mirrors the evening before pushing out | |||
=== RelEng === | === RelEng === | ||
* went well: hotfix signing, no fallout from patch tuesday, vanilla+esr+stub | |||
* room to improve: timing of "go to builds", colo outages, coord w/TB releases | |||
** need action before FF17.0 with double/overlapping ESR releases | |||
* "push to releasetest"... change since CDN. still checking, but expect change in process | |||
* [akeybl] PT (or later) time zone coverage for week 6 builds? | * [akeybl] PT (or later) time zone coverage for week 6 builds? | ||
** instead do "go to build" ~10am PDT, by not doing migration on friday | |||
** migration mozilla-beta -> mozilla-release earlier? | |||
** migration to happen as soon as b6 shipped (wed?) | |||
** [communicate the above at channel meeting] | |||
** 10AM Friday feedback deadline, to go to build | |||
** ship wed morning instead of tues morning? also avoids patch tuesday | |||
* not able to (reasonably) pull broken build from android marketplace | |||
* [akeybl] launch delayed significantly by late filing of {{bug|799473}} – please update AUS to AUS2_PRODUCTION tag | * [akeybl] launch delayed significantly by late filing of {{bug|799473}} – please update AUS to AUS2_PRODUCTION tag | ||
** 40mins-1.5hrs | |||
=== Security === | === Security === | ||
* Providing context about how we're trying to prevent future 16.0.1/16.0.2 type releases | * Providing context about how we're trying to prevent future 16.0.1/16.0.2 type releases | ||
* May want a security repo w/ private tests | |||
=== Marketing & Press === | === Marketing & Press === | ||
* Differing feedback for 16.0.1 and 16.0.2 | * Differing feedback for 16.0.1 and 16.0.2 | ||
* From Product Marketing (unable to attend) nothing to note here other than the slight delay in launch time | * From Product Marketing (unable to attend) nothing to note here other than the slight delay in launch time | ||
* Would be good to record a standard protocol guidelines for when and how we communicate future chemspills, security risks, updates, etc. [PR] | |||
=== Other === | === Other === | ||
== Notes == | == Notes == | ||
* [akeybl] how can we keep users installing the previous version of Firefox if we have to pull the product down? (mobile) | * [akeybl] how can we keep users installing the previous version of Firefox if we have to pull the product down? (mobile) | ||
* [akeybl/Pike] how to catch build failures in l10n early? See also {{bug|800432}} | * [akeybl/Pike] how to catch build failures in l10n early? See also {{bug|800432}} | ||
== Actions == | == Actions == | ||
* RelMgmt - what disabling an Android product means, and a proposal for future instances (re-building the prior version with a higher buildid) - QA & RelEng scheduling impacted | |||
* All - before pulling the trigger on any releases, we need to make sure to have one final conversation | |||
* johnath - review of release-drivers for people who may not be appropriate to see | |||