Firefox is string frozen - sort of! - start your localizations!

[Mike Beltzner]

(followup: mozilla.dev.planning / dev-pl...@lists.mozilla.org)

Hey everyone,

As per the announcement earlier this week, Firefox is now in a string
freeze, pending some final check-ins this evening.

Drivers expect there to be a few more string landings before code freeze
on Tuesday, Jan 29th. All of these will be marked with "late-l10n", as
will any patches which make use of new strings which were landed before
the string freeze. Most of the changes will be in the following areas of
the UI:
- the new dialog for adding bookmarks
- the applications preference pane
- the feed preview and subscription screen

Localizers should feel free to begin their work now. The drivers will
keep the changes to a minimum.

cheers,
mike

[Mike Beltzner]

Mike Beltzner wrote:
> As per the announcement earlier this week, Firefox is now in a string
> freeze, pending some final check-ins this evening.

Specifically, on the following bugs:

https://bugzilla.mozilla.org/show_bug.cgi?id=218142
https://bugzilla.mozilla.org/show_bug.cgi?id=242852
https://bugzilla.mozilla.org/show_bug.cgi?id=408797
https://bugzilla.mozilla.org/show_bug.cgi?id=382447
https://bugzilla.mozilla.org/show_bug.cgi?id=413658
https://bugzilla.mozilla.org/show_bug.cgi?id=303645
https://bugzilla.mozilla.org/show_bug.cgi?id=400061
https://bugzilla.mozilla.org/show_bug.cgi?id=400064
https://bugzilla.mozilla.org/show_bug.cgi?id=404661

cheers,
mike

[Myk Melez]

Mike Beltzner wrote:
> Mike Beltzner wrote:
>> As per the announcement earlier this week, Firefox is now in a string
>> freeze, pending some final check-ins this evening.
>
> Specifically, on the following bugs:

...

> https://bugzilla.mozilla.org/show_bug.cgi?id=303645
> https://bugzilla.mozilla.org/show_bug.cgi?id=400061
> https://bugzilla.mozilla.org/show_bug.cgi?id=400064

I checked in the string changes for these three a few hours ago, before
the freeze, so those don't need late-l10n (unless of course we discover
that we need additional string changes when the code changes land).

-myk

[Mike Beltzner]

Ah, OK. To be clear, that list of bugs *won't* be marked late-l10n, as
they've already been approved to land. We're a little late on our
11:59pm PST deadline due to some internet failings on my part and some
tree failings all around.

cheers,
mike

[Myk Melez]

Mike Beltzner wrote:
> Ah, OK. To be clear, that list of bugs *won't* be marked late-l10n, as
> they've already been approved to land. We're a little late on our
> 11:59pm PST deadline due to some internet failings on my part and some
> tree failings all around.

Err, right, of course, I see now that's what you meant in the original
message. I just misread it.

-myk

[Mike Beltzner]

On 26-Jan-08, at 4:05 AM, Mike Beltzner wrote:

> https://bugzilla.mozilla.org/show_bug.cgi?id=218142
> https://bugzilla.mozilla.org/show_bug.cgi?id=242852
> https://bugzilla.mozilla.org/show_bug.cgi?id=408797
> https://bugzilla.mozilla.org/show_bug.cgi?id=382447
> https://bugzilla.mozilla.org/show_bug.cgi?id=413658

> https://bugzilla.mozilla.org/show_bug.cgi?id=303645
> https://bugzilla.mozilla.org/show_bug.cgi?id=400061
> https://bugzilla.mozilla.org/show_bug.cgi?id=404661

All of the above were checked in today, for what it's worth.

> https://bugzilla.mozilla.org/show_bug.cgi?id=400064

This one was not, as we had to make some modifications to support
pluralization. It will get checked in later and marked late-l10n,
appropriately.

cheers,
mike

[Robert Kaiser]

Mike Beltzner schrieb:

> (followup: mozilla.dev.planning / dev-pl...@lists.mozilla.org)
>
> Hey everyone,
>
> As per the announcement earlier this week, Firefox is now in a string
> freeze, pending some final check-ins this evening.

Is this a freeze for FF3 final or for Beta3 only?

Robert Kaiser

[Mike Beltzner]

The freeze is for Firefox. Every string change from here on in is late-
l10n for the product.

cheers,
mike

[Ted Mielczarek]

On Jan 26, 3:58 am, Mike Beltzner <beltz...@mozilla.com> wrote:
> (followup: mozilla.dev.planning / dev-plann...@lists.mozilla.org)

> Drivers expect there to be a few more string landings before code freeze
> on Tuesday, Jan 29th. All of these will be marked with "late-l10n", as
> will any patches which make use of new strings which were landed before
> the string freeze. Most of the changes will be in the following areas of
> the UI:

I wasn't aware of this. If I land a code change that uses a string
that was preemptively added, I should add the keyword "late-l10n"?
Will I also need driver approval to land it?

-Ted

[Axel Hecht]

Yes, according to beltzner's announcement from Tuesday. Please add the
late-l10n keyword, too.

Axel