Bei der Gruppe, für die Sie eine Mitteilung verfassen, handelt es sich um eine Usenet-Gruppe. Wenn Sie in dieser Gruppe Nachrichten posten, ist Ihre E-Mail-Adresse für jeden im Internet sichtbar
We are currently planning to start building the first release candidate builds shortly after the deadline expires on Monday, November 2 23:59 Pacific time. We will take all locales that are ready (green dashboard) by then and have opted in for this release.
If we decide to do further release candidates, I'll reopen this thread so that you can include further fixes to your locales as you deem necessary.
We're not really there yet with our final story on the web l10n front, as I told some of you on the last weekend in Prague, but our marketing person, Rafael Rebron, and Pascal Chevrel are working hard on that and will update you on this matter in the next few days.
As of now, on the code side, things are already looking great with 32 locales already being green on the dashboard and more hopefully still to come.
If you have any questions, feel free to ask them here.
> We are currently planning to start building the first release candidate > builds shortly after the deadline expires on Monday, November 2 23:59 > Pacific time. We will take all locales that are ready (green dashboard) > by then and have opted in for this release.
> If we decide to do further release candidates, I'll reopen this thread so > that you can include further fixes to your locales as you deem necessary.
> We're not really there yet with our final story on the web l10n front, as > I told some of you on the last weekend in Prague, but our marketing > person, Rafael Rebron, and Pascal Chevrel are working hard on that and > will update you on this matter in the next few days.
> As of now, on the code side, things are already looking great with 32 > locales already being green on the dashboard and more hopefully still to > come.
> If you have any questions, feel free to ask them here.
> We are currently planning to start building the first release candidate > builds shortly after the deadline expires on Monday, November 2 23:59 > Pacific time. We will take all locales that are ready (green dashboard) > by then and have opted in for this release.
> If we decide to do further release candidates, I'll reopen this thread so > that you can include further fixes to your locales as you deem necessary.
> We're not really there yet with our final story on the web l10n front, as > I told some of you on the last weekend in Prague, but our marketing > person, Rafael Rebron, and Pascal Chevrel are working hard on that and > will update you on this matter in the next few days.
> As of now, on the code side, things are already looking great with 32 > locales already being green on the dashboard and more hopefully still to > come.
> If you have any questions, feel free to ask them here.
> We are currently planning to start building the first release candidate > builds shortly after the deadline expires on Monday, November 2 23:59 > Pacific time. We will take all locales that are ready (green dashboard) > by then and have opted in for this release.
> If we decide to do further release candidates, I'll reopen this thread so > that you can include further fixes to your locales as you deem necessary.
> We're not really there yet with our final story on the web l10n front, as > I told some of you on the last weekend in Prague, but our marketing > person, Rafael Rebron, and Pascal Chevrel are working hard on that and > will update you on this matter in the next few days.
> As of now, on the code side, things are already looking great with 32 > locales already being green on the dashboard and more hopefully still to > come.
> If you have any questions, feel free to ask them here.
> Is there a reason why you would need the *SeaMonkey* string updates > for your *Thunderbird* localization?
No, I'm just one of those folks who would go with "Use my latest revision" if I could. No, I don't plan to re-opt in with each and every change in my tree, it's just that the opt-in season isn't over yet, so I though it makes no difference to you.
>> Is there a reason why you would need the *SeaMonkey* string updates >> for your *Thunderbird* localization?
> No, I'm just one of those folks who would go with "Use my latest > revision" if I could. No, I don't plan to re-opt in with each and > every change in my tree, it's just that the opt-in season isn't > over yet, so I though it makes no difference to you.
|
