Status Meetings:2007-01-31:Agenda

From Camino Wiki
Jump to navigation Jump to search

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

General Plans

  • Camino 1.1
  • Camino 1.1b1
    • "early Feb" - Feb is tomorrow; do we want to set a tentative date?
      • UI facing work remaining on bugs we need for 1.1 - 8 nibs and strings bugs, including Password Stealing, 2 Spelling UI bugs, and fixing the pop-up blocker to (at minimum) not auto whitelist
      • 1-2 weeks of work/reviews yet? :(
    • kqueue is back for review round 6
    • spelling UI
    • password stealing is partially written
  • Camino 1.0.4
  • tinderboxen
    • pawn's Tp is [CRASH] - does the timeout need to be increased again?
  • Bookmark loss
  • Weekly Bugs and Queues update
    • r queue remaining high due to lack of personnel; sr queue gets cleared periodically of bugs that matter (most 1.1 bugs or trunk-only fixes)

Specific bugs that need action

1.1 (priority)

  • Bug 343937 Default "unblock popup" behavior should not include adding site to Exceptions List
    • smorgan has new mock-ups for us

Not 1.1 (if there's time)

  • Bug 295755 - Implement Flashblock/CamiFlash as a default Camino preference
    • We need to decide on the preferred (easiest/most easily maintainable long-term) way to integrate Flashblock into our tree:
      N.B. all options require modifying our installed-chrome.txt file and relevant Copy Phase project change for the jar; Flashblock's 1.3 branch is feature-equiv to the 1.5 branch but supports XPFE chrome
      1. Manually build a custom jar each time Flashblock is upgraded and land it in the tree (saves 30K of XUL files and no need to add contents.rdf during build, but someone would have to do it each time)
      2. Land stock Flashblock jar in the tree (need to add contents.rdf during build; 30K of XUL files still in the jar)
      3. Land the Flashblock source files (or pull from Flashblock CVS) and contents.rdf in the tree and build the jar ourself (someone would have to extract these files from a Flashblock jar each time, and if Flashblock ever requires a new file, add that to the camino tree (and modify the
  • Bug 248160 - [l10n] Translate chrome strings on the fly
    • kreeger wants to talk about this
  • Bug 337261 – Review dom_storage build changes on the Camino/1.8 branch
    • Do we want the other stuff? (global storage, comment 3)
  • Bug 361157 - Opening files should open them in a new window
    • Should this be tied to a pref, and if so which one?


Camino 1.1b1

  • Blocking ? (10) -1 since last week (8 have nib or string implications)
  • Blocking + (2) -1 since last week (1 is ReadMe audit, one is awaiting checkin)
  • Blocking - (1) [unchanged] ("prefs slow to open since RSS")

Camino 1.1


  • Review (10) [+2 since last week]
  • Superreview (5) [-4 since last week] (only 2 are 1.1 bugs)