Difference between revisions of "Status Meetings:2006-10-11:Agenda"
Jump to navigation
Jump to search
(→Queries: updating) |
(→Queues: updating) |
||
| Line 44: | Line 44: | ||
==Queues== | ==Queues== | ||
| − | * [https://bugzilla.mozilla.org/request.cgi?action=queue&requester=&product=Camino&type=review&group=type Review] | + | * [https://bugzilla.mozilla.org/request.cgi?action=queue&requester=&product=Camino&type=review&group=type Review] (13) {{greyText|[+7 net since last week]}}<!-- --> |
| − | * [https://bugzilla.mozilla.org/request.cgi?action=queue&requester=&product=Camino&type=superreview&group=type Superreview] | + | * [https://bugzilla.mozilla.org/request.cgi?action=queue&requester=&product=Camino&type=superreview&group=type Superreview] (5) {{greyText|[+2 net since last week]}}<!-- --> |
Revision as of 23:09, 10 October 2006
Wed 11 Oct 9am PDT (16:00 GMT/UTC) in #camino-mtg
Contents
General Plans
- Camino 1.1 Alpha 1
- Hold again or go?
- kqueue not ready yet; this weekend/by Tues hopefully
- No real movement on the pop-up blocker front
- planet says Fx2 RC 3 is Tue Oct 17 and Fx2 release is Tue Oct 24
- Hold again or go?
- What about putting l10ns into Camino source repository? (by Marcello)
- I'd like to spend most of my efforts on the community side of Caminol10n, trying to make it better and more productive. Since I already maintain (in a very clumsy way) a cvs repository of l10n packages and text files, why not put them among Camino's source, so that the ML package might be built directly from that place?
- Pros:
- I shouldn't work on building and distributing, and I would not be a bottleneck as sometimes happened in the past
- Unified Camino build more in line with Mac OS X
- Cons:
- The build system would need be changed
- Moving the bottleneck to coordinating cvs checkins
- Out-of-date translations:
- Stale files on development branches (e.g., an out-of-date BrowserWindow.nib will hork that language) [could be worked around by keeping nightlies En-only]
- Non-updated l10ns still in cvs across branch changes or emergency new strings on a stable branch (e.g., Pirate 1.0.x never gets updated for 1.x, or in the event string changes are needed for 1.0.x+1)
- additional pros/cons in italics by sardisson, who'd really like to see a unified Camino build nonetheless
- l10n of license.r on dmg? Is that feasible tech-wise?
- Tab scrolling landed on the trunk (congrats delliott!) and we're working on follow-up bugs
Specific bugs that need action
Queries
Camino 1.1a1
- Blocking ? (7) [-2 net since last week]
- Blocking + (0) [unchanged]
- Blocking - (0) [unchanged]
Camino 1.1
- Bugs targeted at 1.1 (114) [-2 net since last week]
- Blocking ? (11) [unchanged]
- Blocking + (3) [unchanged]
- Blocking - (0) [unchanged]
- Bugs without target (256) [+12 since last week]
- The above list needs to be at least spot-audited for potential 1.1 issues
- Bugs fixed since last meeting (10) [+2 since last week] (4 bugs were 1.1-targeted; of those, 1 was a 1.1a1 nominee)
Queues
- Review (13) [+7 net since last week]
- Superreview (5) [+2 net since last week]
