Difference between revisions of "Status Meetings:2006-10-04:Agenda"

Revision as of 13:20, 25 September 2006

Wed 04 Oct 9am PDT (16:00 GMT/UTC) in #camino-mtg

Camino 1.1 Alpha 1
Fixing Core-caused breakage in Camino in a timely fashion
- Time it took to get biesi's patch (super)reviewed [4 days], to get autocomplete fix (super)reviewed, to get chardet fix (super)reviewed
- Funky select widgets, missing trunk talkback are out of our hands
- How can we improve? The problems will only increase as xpfe dies....
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 mantain (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
- Cons: The build system should be changed

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

@@ Line 7: / Line 7: @@
 ** Funky select widgets, missing trunk talkback are out of our hands
 ** How can we improve?  The problems will only increase as xpfe dies....
+* 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 mantain (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
+** Cons: The build system should be changed
 ==Specific bugs that need action==