Status Meetings:2007-01-31:Agenda
Jump to navigation
Jump to search
Wed 31 Jan 9am PST (17:00 GMT/UTC) in #camino-mtg
Contents
General Plans
- Camino 1.1
- See User:sardisson/Camino 1.1 and User:sardisson/Camino 1.1/Priority List for bugs
- Only nn crashes from a2 in 3 weeks (nn unique users)
- Camino 1.1b1
- "early Feb" - Feb is tomorrow; do we want to set a tentative date?
- kqueue is […]
- spelling UI
- password stealing is partially written
- how are we doing on UI facing work remaining on bugs we need for 1.1
- Camino 1.0.4
- tinderboxen
- Bookmark loss
- Weekly Bugs and Queues update
Specific bugs that need action
1.1 (priority)
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
- Manually build a custom jar each time Flashblock is uprgaded 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)
- Land stock Flashblock jar in the tree (need to add contents.rdf during build; 30K of XUL files still in the jar)
- Land the Flashblock source files 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 jar.mn?)
- We need to decide on the preferred (easiest/most easily maintainable long-term) way to integrate Flashblock into our tree:
- 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?
Queries
Camino 1.1b1
Camino 1.1
- Bugs targeted at 1.1
- Blocking ?
- Blocking +
- Blocking -
- Bugs without target
- The above list needs to be at least spot-audited for potential 1.1 issues