Status Meetings:2008-04-02:Agenda
Jump to navigation
Jump to search
Wed 02 apr 9am PDT (17:00 GMT/UTC) in #camino-mtg
Contents
General Plans
- Camino 1.6b4
- Released last Thursday
- Talkback (all 1.6b4 crashes—28 so far)
- Need to make sure we're getting enough user coverage
- Need to make sure we have a freeze/RC period before we release
- Camino 1.6
- Scoping
- swupdate: only minor stuff left, as long as nothing new appears with b3 testing
- Ts regression Bug 405542), testing via b3
- swupdate: only minor stuff left, as long as nothing new appears with b3 testing
- What 10.5 UI integration fixes do we want?
- We'll take the other toolbar icons if they're ready
- stefanh has a new .DS_Store that should fix the dmg window on 10.5s with path bar showing
- Releases:1.6:l10n shows l10n status; that plus website changes are all that really block
- Release notes in progress
- Gecko 1.8.1.14 coming as a firedrill
- Can someone fix cl's nib for the prefPane docs? (Bug 384800 comment 18, 19, 26)
- Scoping
- Camino 1.5.5
- Not planning release of 1.5.x
- Talkback for 1.5.5
- Still cleaning up stuff from the website switch; file bugs against Product Site if you see anything.
- Camino 2.0
- Rough scoping doc at Development:Planning:Camino 2.0
- Stuart's started triaging the 2.0 list (3 criteria: regressions, make life better now, someone working on it)
- Stuart has started on the regressions
- Cocoa Widget "fixes" are making life pretty rough
- Summer of Code 2008
- Our suggestions; students apply this week (deadline extended to next Mon)
- Tinderboxen
- boxset currently offline because Sam has no internet; please treat the tree as closed
- boxset stopped reporting to tinderbox two Thurs ago - Bug 425138
- 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 on loan to Sunbird
- 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
- Queues in pretty good shape
Specific bugs that need action
1.6b5pre/1.6pre
- nothing specific
1.5.6
- nothing right now; there are a couple of bugs if we do one
Other (if there's time)
- 10.5 Visual UX
- Bookmark bar - Bug 401340
- Tab bar
- Toolbar icons - Bug 384725
- We have a designer working on polishing
- App icon lines - Bug 402967
- dmg scrollbar with path bar - Bug 423474
- 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
- 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.
Queries
Camino 1.6
- Bugs targeted at 1.6 (7) [unchanged] (almost all non-code)
- Blocking ? (2) [+1 since last week] (bugs not on the 1.6 list that need evaluation)
- Blocking + (3) [unchanged]
- Blocking - (4) [unchanged]
- Bugs without target (604) [+12 since last week]
- Bugs fixed since last meeting (12) [+9 since last week] (9 were 1.6-targeted, 2 were website, 1 was trunk-only)
Queues
- Review (7) [-1 since last week]
- Superreview (1) [-2 since last week]