Platform/2009-07-21: Difference between revisions
< Platform
Jump to navigation
Jump to search
Samuelsidler (talk | contribs) |
|||
| Line 97: | Line 97: | ||
* 64-bit Mac OS X port blocked on gfx {{bug|493280}}. | * 64-bit Mac OS X port blocked on gfx {{bug|493280}}. | ||
** current intention is to land 493280 on trunk right after 1.9.2 branches; is it wanted earlier? | ** current intention is to land 493280 on trunk right after 1.9.2 branches; is it wanted earlier? | ||
* Cocoa NPAPI event model | * Cocoa NPAPI event model basically finished, part of it landed, the rest under review. | ||
* Steven Michaud fixed two topcrashers: {{bug|503196}} and {{bug|503391}}. | |||
=== JS === | === JS === | ||
Revision as of 18:00, 21 July 2009
« previous week | index | next week »
Notices / Schedule
- shipping today
- work on your blockers
- code freeze on August 4
- please request approval before landing
- Over 35 MILLION downloads so far!
- shipped an early release last week do to 0-day
- using the new flags for triage
- goal of this release should be a quick-turnaround that:
- topcrash fixes, security/stability patches
- narrow scope, small changes
- contrary to some reports on the Internet, this is the usual process for Firefox and software releases; the 3.5 release was strong, stable and solid, and feedback has been extremely positive. Near the end of the release we become extremely conservative about patches to accept; the 3.5.1 release is a quick update to fold in some patches that came up late in the 3.5 release cycle.
- we will be going through approval1.9.1.1 flags and triaging them; no need to change them to approval1.9.1.2 flags
Firefox 3.6a1
- code freeze 21-July?
Blocker Report
Gecko 1.9.1.2 / Firefox 3.5.2
- 32 blocking1.9.1:2+, ? nominations
- 9 1.9.1:2+ blockers left without a fix
Gecko 1.9.2 / Namoroka
- 298 open blocking1.9.2?, 35 open blocking1.9.2+
- 79 open blocking-firefox3.6?, 3 open blocking-firefox3.6+
Browser / Front End
- posted the Q3 team goals for Firefox on the wiki, as well as the evaluation of last quarter's goals
- Firefox.next
- moving on to TSnap bugs which aim to make Firefox observably faster
- some of us are working on WinCE compatibility issues
- also returning to polish bugs and exploratory sprints
- Reminder to review the Firefox.Next plan and add your comments/feedback on the discussion page or in the dev-apps-firefox thread
- Polish update: Firefox is 59% shiny (0% change)
- Thanks go to: dougt (P2), dao (P2)
- 46 remaining easy polish bugs (whiteboard [polish-easy])
- 38 remaining hard polish bugs(whiteboard [polish-hard])
GFX Update
- bug 753 - landed!
- Landing bug 753 means that it's now possible to make informed decisions about the individual pieces that depend on it.
- Decode-on-draw is working pretty well, but has a lot more bugs to go. Bobby Holley is going to be sprinting on it this week, and we'll likely be able to make a call on it this time next week.
- Aero peek backend, bug 501490, is just awaiting review, but also depends on some other bugs. Will be ready.
- Backend code also contains a taskbar framework that other Windows 7 enhancements depend on.
- Windows 7 enhancements that depend on Aero peek's taskbar/superbar framework:
- Aero peek frontend bug 474056 is coming along, and will likely be ready in time.
- Download status in the superbar, bug 474060, probably won't make it for 1.9.2, but sid0 is working on it.
- Jumplists, bug 473045. Should be in 1.9.2, will probably make it?
- All the above should be ready by mid-August - soon enough?
- Windows/Windows 7 enhancements that don't depend on taskbar/superbar:
- Window docking on Windows 7, bug 489258, is just waiting on review for both 1.9.1 and 1.9.2.
- Parental Controls:
- bug 355555 - Content blocking by parental controls. In progress.
- bug 423587 - Extension manager install blocking parental controls - up for review.
- Cleartype
- bug 504698 - Windows XP doesn't have Cleartype (subpixel text AA) enabled by default, which has upset some downloadable font-using authors. Fix is going to be to add a hidden pref, default to on, to force Cleartype on downloadable fonts. This will be submitted for 1.9.1 and 1.9.2.
- Question: Do we want to default Cleartype on for all content? That's what IE does. (Probably want to check in backend support for this, then let products make their own call. 1.9.2 only.)
Other news:
- topcrasher bug 470487 fix seems to have worked! Backport to 1.9.1?
Layout Update
- Patches on 1.9.2 radar
- Compositor phase 1
- CSS gradients
- CSS background-size
- bz's framelist cleanup
- Core Text?
- wanted for better OpenType support (esp. Arabic, relevant for @font-face use), and for broader testing as Core Text is required for 64-bit
- requires moving builds to 10.5 SDK (bug 504179), then adding --enable-coretext configure option to mozconfig
- changing SDK introduces risk of incompatibility with 10.4; need to maintain testing on 10.4 until we officially drop it as a supported OS
- known sqlite issue on 10.4 in bug 423691 (has workaround)
- Patches probably waiting for post-1.9.2
- Font system unification cleanup
- Remove float placeholder splitting
- Disable interruptible reflow for 1.9.2 default
Content Update
- No major updates this week.
Mac OS X Update
- Markus Stange is very close to having a completed patch for fullscreen in 1.9.2, bug 420491.
- 64-bit Mac OS X port blocked on gfx bug 493280.
- current intention is to land 493280 on trunk right after 1.9.2 branches; is it wanted earlier?
- Cocoa NPAPI event model basically finished, part of it landed, the rest under review.
- Steven Michaud fixed two topcrashers: bug 503196 and bug 503391.
JS
- GC plan underway JavaScript:SpiderMonkey:GC_Futures
- converging on JIT with Adobe
- measure, measure, patch
Security
Electrolysis
Phase II beginning: need project owners and mentors for tasks on this list. Please join mozilla.dev.tech.dom for project discussions.
cjones has basic IPDL docs available. We're expanding the docs as we go, so please contact him (or the list) with questions.
Bent did a "remote xpcshell" for prototyping and testing: commands can be issued to run in the parent or the child process. we also created an "IPC test harness" which can be used to experiment with IPC protocols (see the IPDL docs).
bsmedberg doing local buildbots until RelEng can hook up a full project... reporting to tinderbox.
Tree Management
- Places project branch handed over to sdwilsh yesterday. Please ramp up load gently ! Details in bug 459269
- has usual builds/unittests/talos
- http://tinderbox.mozilla.org/showbuilds.cgi?tree=Places
Roundtable
- Everyone should read other teams' goals.
- stabilizing mozilla-central for a 1.9.2 branch / 1.9.2 alpha (beltzner)
- cleaning up after large landings: interruptible reflow, content sink, cairo rewrite, focus update, asynchronous location bar
- reducing instability
- aiming to freeze for tag and branch to mozilla-1.9.2 on July 31st
- this will be used for Fennec 1.0, Firefox 3.6
- afterwards, trunk to open with staged landings for large changes
- multi-state flag for blocking-1.9.1.x:
- blocking1.9.1? - nominated
- blocking1.9.1- - not blocking
- blocking1.9.1needed - needs to go on a security/stability release
- blocking1.9.1.2+ - blocking 1.9.1.2
- blocking1.9.1.3+ - blocking 1.9.1.3
- ...etc
- multi-state flag for status-1.9.1.x:
- status1.9.1needstriage - needs driver attention
- status1.9.1unaffected - doesn't affect the 1.9.1 branch
- status1.9.1wanted - fix wanted for 1.9.1 branch
- status1.9.1wontfix - wontfix for 1.9.1 branch
- status1.9.1.2-fixed - fixed in 1.9.1.2
- status1.9.1.3-fixed - fixed in 1.9.1.3
- ...etc