Seth Bindernagel writes, “Last week, a subset of the l10n-drivers team met in Paris to discuss many things related to l10n, including a review of goals that had been sent last November before the lead-up to the release of Firefox 3. The goals were ambitious and listed many ways in which the team could create positive impact. Part of our work week was to review these goals and to find out what we did well, didn’t do well, and could do better as we create goals for the upcoming quarter.” Seth’s weblog post continues on to go through each goal in detail, discussing what went well and where things can be improved in the future.

We’ve seen reports that Firefox 3.0.1 has somehow broken compatibility for many add-ons. This is not the case. When developers publish their add-ons they declare a compatibility range for it that looks something like this “2.0 to 3.0.*”. This example range says that the add-on is compatible with Firefox versions ranging from 2.0 through all maintenance releases of Firefox 3. What appears to have happened with the release of Firefox 3.0.1 is that some add-on authors put “3.0″ instead of “3.0.*” (note the star) in their compatibility range, which means their add-ons do not appear to be compatible with Firefox 3.0.1 even if they really are. If your add-on was flagged as incompatible with Firefox 3.0.1, you may want to double-check the maxVersion you have specified. More information is available at Basil Hashem’s weblog.