Difference between revisions of "Firefox3/StatusMeetings/2008-05-20"
From MozillaWiki
< Firefox3 | StatusMeetings
m (→QA Status/Topics) |
(→Platform Post 1.9) |
||
Line 19: | Line 19: | ||
== Platform Post 1.9 == | == Platform Post 1.9 == | ||
− | * Work Week post 1.9 tasks/work items [http://spreadsheets.google.com/pub?key=pF_tMaWf14QxNYvZaPTvsGA | + | * Work Week post 1.9 tasks/work items lists: [http://spreadsheets.google.com/pub?key=pF_tMaWf14QxNYvZaPTvsGA gfx] [http://spreadsheets.google.com/pub?key=pF_tMaWf14QyuXltBtJtYdw layout] [http://spreadsheets.google.com/pub?key=pF_tMaWf14QywtyDtOwkzdg content] |
− | * Please create bugs for these (tracking or whatever), and make sure those docs are updated. | + | * Please create bugs for these (tracking or whatever), and make sure those docs are updated. |
== Localization == | == Localization == |
Revision as of 18:25, 20 May 2008
« previous week | index | next week »
Firefox 3/Gecko 1.9 Meeting Details
- Tuesdays - Firefox 3 - 11:00am Pacific, 2:00pm Eastern, 18:00 UTC
- Mozilla Building S - Central Area
- 650-903-0800 or 650-215-1282 x91 Conf# 217 (US/INTL)
- 1-800-707-2533 (pin 369) Conf# 217 (US)
- irc.mozilla.org #granparadiso for backchannel
Contents
Firefox 3: issues for final ship
- Blocker nominations: platform, frontend & toolkit
- Bugs marked as RC2 considerations
Analysis
- fill this section in with notes!
Platform Post 1.9
- Work Week post 1.9 tasks/work items lists: gfx layout content
- Please create bugs for these (tracking or whatever), and make sure those docs are updated.
Localization
- most screenshots are done and photoshoped for all locales (about 500 images).
- logo icons for getting started pages are on the website for all locales
- most of web design bugs for localized in-product pages are fixed, the last important web bug is the creation of an additional method to our firefoxDetails php class to generate new download boxes for localized pages (html markup change)
- we have a dozen pages still unfinished (out of 450) for the locales we ship in June. Potential locales with a future 3.0.x have barely started localizing the in-product pages.
- focus is now less on in-product pages and more on the redesign of mozilla europe and update of firefox product pages
8 outstanding approval request, 5 of which Axel would see as arguments in favor of RC2
QA Status/Topics
- Notable bugs
- This week's bugs were encountered during RC1 testing. More detailed results here.
- bug 433340 – bookmark dialog covers candidate window when using IME. Status: recommended for RC2 with patch in place.
- Filed bug 434491 – Several ns*Accessible classes leak on simple paragraph with 1 link in it. Status: Assigned to jonas
- Filed bug 433440 – Setting Fx to default browser on installer does not launch browser. Looks like a dupe of bug 395891 and bug 295248
- Renom'd bug 433298 EULA cut off checkbox/buttons on bottom - unusable on small (EeePC) screens for blocking-firefox3. Linux users in this mode have a minimal way to move forward with the installer. Duped bug 433627 in the process.
- bug 433796 JavaScript component does not have a method named: "observe"' when calling method: [nsIObserver::observe]
- bug 433748 Error: this._processor is null
- bug 433370 – NS_ERROR_ILLEGAL_VALUE in [nsITreeView::getCellText]
- I get a page alert and a dialog coming down on SSL Error exceptions. Cannot find the bug but the issue is
- Favicons are not imported from Safari bug 326701
- bug 420449 (unable to drag folders in bookmarks toolbar)
- bug 433795 (error in the console when trying to move folder)
- bug 421775 (moving items in the bookmarks library)
- bug 433934 (Name field of History Entries should not look like it can be edited)
- bug 433959 (Page info for mozilla.com shows a cnn.com cookie)
- bug 433975 (session restores to wrong session)
- bug 433942 – Focus lost when going "Back" a page after dismissing a notification bar
- bug 433605 - NS_ERROR_NOT_AVAILABLE [nsIChannel.contentType]
- Confirming during FFT: bug 324334 - Cannot switch to Error Console in the "Window" menu
- This week's bugs were encountered during RC1 testing. More detailed results here.
- General QA
- Shipped RC1 with baseline QA pass last week
- Working on in-depth testpass for this week
- See full list of areas covered for RC1
- Currently ~60% completed
- Still collecting feedback from hendrix and newsgroups. Seeing a few common reports:
- Losing bookmarks after updating from beta 5
- incompatible extensions, some plugins aren't working
- Testday this week on RC1 part 2. Please join #testday from 7am-5pm PDT to assist with questions.
- Leak Testing Update
- Filed 1 new bugs
- bug 433360 - Firefox leaks when uninstalling the Yahoo Mail Notifier Extension
- Filed 1 new bugs
- Topsite Automation
- reproducible:
- linux malloc and jemalloc crash loading http://v.788111.com/Video.html
- Filed bug bug 433758
- not reproducible:
- linux malloc and jemalloc crash after full scan of istockphoto.com
- mac os x pcc
- crash loading http://www.miniclip.com/toons/?open
- crash loading http://www.flurl.com/search/site/445/
- reproducible:
- Topcrashes Analysis
- The bulk of our top 10 crashes appear to be driven by plugins and extensions. Specifically, 1, 2, 4 and 7. Our number 3 topcrash, bug 433525, is a recent regression which we should probably respin for. The bug has a patch ready to go.
- There's also another recent regression (bug 434401) that may be happening in thebes or layout. dbaron believes thebes.
- We're also seeing a startup crash after upgrading to RC1 from beta 5. This is bug 434403 and seems to be a recent regression. While we saw this crash in beta 5 (presumably from upgrading from beta 4), it's much greater this release and happens at a different address. I think we should investigate and try to get this fixed in an RC2.
- For more information on crash tracking, see the wiki page.
Round table
- Build infrastructure maintenance work should be done by end of today. After midnight, any problems, file bug as usual.
- Physical room for meeting next week: sofa area of building K?
(Please note: The RC2 decision will *not* be made at this meeting, just a recommendation; the final decision cannot be made until the RC1 build has had at least a week of public feedback, and until QA has signed off on their full testing suite.)
- make a recommendation on RC2, choosing from one of the following options:
- Build RC2: identify which bugs are the minimal set required for RC2, and start planning for code time, proposed freeze time, proposed build time, and proposed QA testing time required before we can publish it. Again, RC2 would require at least 5 days of public feedback before we could make a shipping decision based on it.
- Do Not Build RC2: identify which bugs are required for Firefox 3.0.1 which would be released 4-6 weeks after we ship Firefox 3.