Firefox/Aurora/2011-05-26: Difference between revisions
Jump to navigation
Jump to search
(→Agenda) |
|||
(8 intermediate revisions by 3 users not shown) | |||
Line 2: | Line 2: | ||
* Status | * Status | ||
** Firefox 6.0a2 Nightly -> Aurora Merge being tested by QA -- no major issues found -- expect sign-off by EOD tomorrow - | ** Firefox 6.0a2 Nightly -> Aurora Merge being tested by QA -- no major issues found -- expect sign-off by EOD tomorrow (ashughes) | ||
*** Plan to start the release process on Friday @ 10:00am. | |||
*** Updates should be available from 5.0a2 -> 6.0a2. | |||
**** Will probably be available around noon PDT. | |||
*** John O will file a bug. We would like the updates ready before 10:00am tomorrow. {{bug|660086}} filed. | |||
** l10n: which locales are based on m-c, and which locales are based on aurora (axel, joduinn) | ** l10n: which locales are based on m-c, and which locales are based on aurora (axel, joduinn) | ||
*** for technical testing, we know we want at least "ar" and "en-US" on mozilla-central | *** for technical testing, we know we want at least "ar" and "en-US" on mozilla-central | ||
** move aurora, beta repo/remove symlinks finished last night. Done. (joduinn) {{bug|652229}} | |||
* Triage | * Triage | ||
** Can we steal a piece of the Aurora triage time to take a look at the stability situation and crasher tracking bugs for the Beta channel? I think we have a more pressing set of concerns there than we do with early Aurora triage. - Asa | ** Can we steal a piece of the Aurora triage time to take a look at the stability situation and crasher tracking bugs for the Beta channel? I think we have a more pressing set of concerns there than we do with early Aurora triage. - Asa | ||
==Action Items== | |||
* Enable updates on auroratest for FF5.0a2-->FF6.0a2. {{bug|660086}} | |||
* l10n: which locales are based on m-c, and which locales are based on aurora (axel, joduinn) | |||
** Filed {{bug|655129}} | |||
==Beta Crashes== | |||
* Not really meant to be part of this meeting but we have identified a number of top crashes that did regress in 5.0. These are not new signatures but our research has found a significant increase in volume. | |||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=645775 Bug 645775] - checked in a patch we thinks fixes this. | |||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=602803 Bug 602803] | |||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=605033 Bug 605033] - checked a patch into Beta. | |||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=595635 Bug 595635] |
Latest revision as of 23:21, 27 May 2011
Agenda
- Status
- Firefox 6.0a2 Nightly -> Aurora Merge being tested by QA -- no major issues found -- expect sign-off by EOD tomorrow (ashughes)
- Plan to start the release process on Friday @ 10:00am.
- Updates should be available from 5.0a2 -> 6.0a2.
- Will probably be available around noon PDT.
- John O will file a bug. We would like the updates ready before 10:00am tomorrow. bug 660086 filed.
- l10n: which locales are based on m-c, and which locales are based on aurora (axel, joduinn)
- for technical testing, we know we want at least "ar" and "en-US" on mozilla-central
- move aurora, beta repo/remove symlinks finished last night. Done. (joduinn) bug 652229
- Firefox 6.0a2 Nightly -> Aurora Merge being tested by QA -- no major issues found -- expect sign-off by EOD tomorrow (ashughes)
- Triage
- Can we steal a piece of the Aurora triage time to take a look at the stability situation and crasher tracking bugs for the Beta channel? I think we have a more pressing set of concerns there than we do with early Aurora triage. - Asa
Action Items
- Enable updates on auroratest for FF5.0a2-->FF6.0a2. bug 660086
- l10n: which locales are based on m-c, and which locales are based on aurora (axel, joduinn)
- Filed bug 655129
Beta Crashes
- Not really meant to be part of this meeting but we have identified a number of top crashes that did regress in 5.0. These are not new signatures but our research has found a significant increase in volume.
- Bug 645775 - checked in a patch we thinks fixes this.
- Bug 602803
- Bug 605033 - checked a patch into Beta.
- Bug 595635