Platform/2008-11-11: Difference between revisions

fix prev/next links
(fix prev/next links)
 
(17 intermediate revisions by 6 users not shown)
Line 1: Line 1:
<small>[[Platform/2008-10-28|&laquo; previous week]] | [[Platform|index]] | [[Platform/2008-11-11|next week &raquo;]]</small>
<small>[[Platform/2008-11-04|&laquo; previous week]] | [[Platform|index]] | [[Platform/2008-11-18|next week &raquo;]]</small>


=== Details ===
=== Details ===
Line 10: Line 10:
=== Notices / Schedule ===
=== Notices / Schedule ===
* Recurring test failures have kept the tree closed; if you can help, join #developers in hunting them down (also: please remember to run tests locally before checking in!)
* Recurring test failures have kept the tree closed; if you can help, join #developers in hunting them down (also: please remember to run tests locally before checking in!)
** bsmedberg is preparing a collation of orange causes, see [[Tinderbox/Nov-2008-Orange-Compendium]]. There are at least 4 random but relatively consistent causes of orange, and mac slave02 is perma-orange with something that appears to be focus issues.
** bugs filed: {{bug|464138}}, {{bug|464286}}, {{bug|464290}}, {{bug|464302}}, ... (need to file a few more)
* See [[Firefox3.1/Security|the security review schedule]] page to get your review scheduled ASAP!
* See [[Firefox3.1/Security|the security review schedule]] page to get your review scheduled ASAP!


Line 31: Line 33:


* performance issues being tracked
* performance issues being tracked
** ''insert bugs here''
** <del>fsync changes</del> ''(done!)''
** {{bug|462973}} - 50ms increase in Ts 2008-11-02 am, no apparent cause?
** {{bug|437829}} - APNG throbber chews a lot of CPU on older computers
 
* polish issues being tracked
** [http://tinyurl.com/5e9dd7 "hard" polish bugs]
** [http://tinyurl.com/5jz3hv "easy" polish bugs]


=== GFX 1.9.1 Update ===
=== GFX 1.9.1 Update ===
Line 40: Line 48:
=== Layout 1.9.1 Update ===
=== Layout 1.9.1 Update ===
* [http://tinyurl.com/6zjp33 1.9.1 Layout Bugs]
* [http://tinyurl.com/6zjp33 1.9.1 Layout Bugs]
* might need some reprioritizing work


=== Content 1.9.1 Update ===
=== Content 1.9.1 Update ===
Line 46: Line 55:
=== JS 1.9.1 ===
=== JS 1.9.1 ===
*[http://tinyurl.com/5gmg8y JS 1.9.1 Bugs]
*[http://tinyurl.com/5gmg8y JS 1.9.1 Bugs]
Entirely focused on remaining JIT fixes.


=== Mobile 1.9.1 Update ===
=== Mobile 1.9.1 Update ===
Line 55: Line 66:


==== Security Reviews ====
==== Security Reviews ====
=== QA Update ===
* Tracking [https://wiki.mozilla.org/QA/Firefox3.1/TestPlan#Blocking_Beta_2_Issues top Blocking beta 2] issues
* Beta 1 [https://wiki.mozilla.org/QA/Topcrashes#Current_topcrashes_being_tracked_3.1b1 Topcrashes update] (ss)
** Fix for #1 landed in b2. Potential fix for #2, #4, #7, and #8 (maybe #11) landed for b2. Some contrast applies from previous update. Also had a potential fix land for #10 and #15 for b2.
* Running javascript automation on [https://wiki.mozilla.org/QA:Home_Page:Firefox_3.0_TestPlan:Leaks:Topsites Global Topsites] for leak/crash/asserts (tomcat)
** A list of 66 dependent bugs found [https://bugzilla.mozilla.org/showdependencytree.cgi?id=455273&hide_resolved=1 here]. 
** Blocking Final Release: {{Bug|463377}} - Fatal assertion on topsites (baidu.com, ebay.com, www.megarotic.com, etc) in String_p_match
** Q. Which 1.9.1/3.1 new areas would you like to see focused leak testing coverage?


=== Roundtable ===
=== Roundtable ===
* Test failures are taking a lot of time
** what can developers do, pre-checkin?
*** run tests, locally, eventually on tryserver
** what do sheriffs need to do, post-checkin?
*** log all test failures so we can correlate recurrences
** can [[TinderboxTLC]] be updated with better information?
*** yes, see above
* State of late-compat bugs?
** bug list with late-compat is very small and seem to be all wontfix/doc issues
** [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=late-compat&resolution=DUPLICATE&resolution=---&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=]
** is that accurate?  Are there any other things planned that might break extensions?
* Next milestone: RC1 or Beta 3?
** a third beta has been proposed in order to get a full feedback cycle on things like TraceMonkey, Speculative Parsing, Private Browsing UI
** would contain ''no new features'' just changes based on feedback
** ''thoughts?''
canmove, Confirmed users, Bureaucrats and Sysops emeriti
1,334

edits