Status Meetings:2008-03-19:Agenda

From Camino Wiki
Jump to: navigation, search

Wed 19 Mar 9am PST (17:00 GMT/UTC) in #camino-mtg

Contents

General Plans

  • Camino 1.6b3
    • Closing in on code-complete; need to decide on the remaining ? noms and schedule mento
    • Working on follow-ups from recent big landings
    • Feature/l10n freeze is already in effect; need bookmark/search l10n policy finished - Bug 411371
    • What 10.5 UI integration fixes do we want?
      • We'll take the other toolbar icons if they're ready
    • Watch changes to perf when landing nibs
  • Camino 1.6
    • Gecko 1.8.1.13 planned for 25 Mar
    • Scoping
      • swupdate: only minor stuff left, as long as nothing new appears with b3 testing; smokey/sam working on getting the script on the site
        Ts regression Bug 405542), appcast script (Bug 401474), testing via b3
      • feed-handlers
        need to exec them for them to be useful (Bug 415319)
  • Camino 1.5.5
    • Hopefully last release of 1.5.x
    • Talkback for 1.5.5
      • Flash is #1
      • Crash on quit ("pass-the-buck" Core Bug 349463) is #2 (bsmedberg has a trunk patch, got sr-)
      • #3 is assorted 0xfffeff18 crashes (crashing deep in Apple code, various Kits, Frameworks and Toolboxes)
      • #4 is libobjc related to plug-ins
      • #5 is Cocoa (mostly QT and other plug-ins)
    • Still cleaning up stuff from the website switch; file bugs against Product Site if you see anything.
  • Camino 1.6b2
    • Talkback (all 1.6b2 crashes—only 120 so far, +13 since last week)
    • Need to make sure we're getting enough user coverage (i.e., more than 1.6a1)
  • Summer of Code 2008
  • Tinderboxen
    • something's wrong on cb-xserve01; reboot didn't help - Bug 421031
    • no new news on binus or maya?
    • ss has replacement minis for binus (to run 10.3) and mayaTrunk; mini-binus is in the colo but not accessible(?); mini-mayaTrunk will go to the colo after Christmas(?)
    • cb-miniosx01 has Ts disabled due to paging/low installed RAM
    • we should think about setting up a testerbox to catch Core bugs breaking embedding APIs (mini-mayaTrunk alternate builds?)
  • Dev docs
    • Still some issues with the sample code and/or nib for the sample prefPane
    • Can we get a quick list of some examples in our code (mxr links) of various ways of
      • Calling private APIs
      • Writing safe code for latest-OS-only features
      Add here; we're getting more patches wanting to do these things, so even if "the" solution cannot be prescribed, examples of various situations and techniques will help
  • Weekly Bugs and Queues update
    • r queue still a bit high, but we're still fixing bugs; need to concentrate on finishing 1.6b3 this week

Specific bugs that need action

1.6b3pre

  • nothing specific

1.5.6

  • nothing right now; there are a couple of bugs if we do one

Other (if there's time)

  • Trunk
    • Need to keep an eye on trunk regressions, determine if they're Camino-only or partly/wholly Core, and consider requesting blocking1.9? for the latter set.
      • It's pretty scary out there right now
    • xpfe cleanup
      • see older Agendas if you're interested

Queries

Camino 1.6b3

Camino 1.6

Queues

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox