Platform/2008-11-11: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(fix prev/next links)
 
(7 intermediate revisions by 4 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 11: Line 11:
* 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.
** 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}}, ...
** 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 48: 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 68: Line 69:
=== QA Update ===
=== QA Update ===
* Tracking [https://wiki.mozilla.org/QA/Firefox3.1/TestPlan#Blocking_Beta_2_Issues top Blocking beta 2] issues
* 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)
* 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.  
** 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)
* Running javascript automation on [https://wiki.mozilla.org/QA:Home_Page:Firefox_3.0_TestPlan:Leaks:Topsites Global Topsites] for leak/crash/asserts (tomcat)
Line 78: Line 79:
* Test failures are taking a lot of time
* Test failures are taking a lot of time
** what can developers do, pre-checkin?
** what can developers do, pre-checkin?
*** run tests, locally, eventually on tryserver
** what do sheriffs need to do, post-checkin?
** what do sheriffs need to do, post-checkin?
*** log all test failures so we can correlate recurrences
** can [[TinderboxTLC]] be updated with better information?
** 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?
* Next milestone: RC1 or Beta 3?

Latest revision as of 21:25, 17 November 2008

« previous week | index | next week »

Details

  • Tuesday - 11:00am Pacific, 2:00pm Eastern, 19:00 UTC
  • Mozilla Building S - <script> conference room
  • 650-903-0800 or 650-215-1282 x91 Conf# 8605 (US/INTL)
  • 1-800-707-2533 (pin 369) Conf# 8605 (US)
  • irc.mozilla.org #shiretoko for backchannel

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!)
  • See the security review schedule page to get your review scheduled ASAP!

Firefox 3.1 Update

  • over the last week the following things landed
    • new Clear Recent History function to allow more fine grained history removal
    • new "Forget About this Site" function to completely remove records of a site
    • Clear Private Data UI
  • performance issues being tracked
    • fsync changes (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

GFX 1.9.1 Update

  • GFX blocking 1.9.1+
  • GFX wanted 1.9.1+
  • Down to 7 blocking bugs -- 3 font-face (one being support on Linux), 1 mac fonts bug (only a mild blocker), 1 pixman perf win (sse2), 2 imglib bugs. Also one mobile bug that probably isn't a 1.9.1 blocker.

Layout 1.9.1 Update

Content 1.9.1 Update

JS 1.9.1

Entirely focused on remaining JIT fixes.

Mobile 1.9.1 Update

General 1.9.1 Updates

Security

Security Reviews

QA Update

  • Tracking top Blocking beta 2 issues
  • Beta 1 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 Global Topsites for leak/crash/asserts (tomcat)
    • A list of 66 dependent bugs found 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

  • 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
    • [1]
    • 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?
Retrieved from "https://wiki.mozilla.org/index.php?title=Platform/2008-11-11&oldid=116952"