Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

L10n locked down -- Re: Reminder - FF2 RC2 Code Freeze 9/29/2006 at 9AM PDT

0 views
Skip to first unread message

Axel Hecht

unread,
Sep 29, 2006, 3:07:26 AM9/29/06
to
Hi,

as of now, the l10n repository is locked down, zero Kelvin.

I'd like to ask folks in mail/calendar to not check-in while we're doing
RC2 as well, it just makes our life easier.

For those locales that have missed 2.0, we don't exactly know when we'll
open up the branch for you, but we do know that we want to do that
rather sooner than later. I guess we'll do so on short notice as soon as
we feel that we don't have to respin l10n for 2.0.

I'll open up the tree for mail/calendar after RC2 is built and tagged.

Thanks to everyone.

I do see a plethora of work coming up for build and QA :-). Oh, and
justin is looking for additional mirror resources.


Axel

Mike Schroepfer wrote:
> Hi Folks,
>
> Just a friendly reminder that tomorrow is our code freeze for RC2. As
> of this writing the only approved patch waiting to land is:
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=354670
>
> If you have any issues that you believe are show stoppers for the
> release please let us know asap.
>
> Mike

Simon Paquet

unread,
Sep 30, 2006, 6:52:03 AM9/30/06
to
And on the seventh day Axel Hecht spoke:

>Hi,
>
>as of now, the l10n repository is locked down, zero Kelvin.
>
>I'd like to ask folks in mail/calendar to not check-in while we're doing
>RC2 as well, it just makes our life easier.

Pike, we (Sunbird/Lightning team) have a release coming up, that is at
least as important to us as Firefox 2 is important for you and the
Mozilla Corporation.

And since we'd like to tag the /l10n repository on October 03 for the 1.8
branch (from which we'll release Lightning, Sunbird will come from its
own branch which originates from the 2006-09-27 trunk), this is really a
major showstopper for us.

I understand your desire to keep everything nice and tidy, but I fail to
see how checkins to /l10n/ab-CD/calendar could somehow affect FF2.

Therefore I would really appreciate it, if you could revise your
statement above.

Thanks in advance
Simon
--
Sunbird/Lightning Website Maintainer:
http://www.mozilla.org/projects/calendar
Sunbird/Calendar blog: http://weblogs.mozillazine.org/calendar

Axel Hecht

unread,
Sep 30, 2006, 10:57:04 AM9/30/06
to
Simon Paquet wrote:
> And on the seventh day Axel Hecht spoke:
>
>> Hi,
>>
>> as of now, the l10n repository is locked down, zero Kelvin.
>>
>> I'd like to ask folks in mail/calendar to not check-in while we're doing
>> RC2 as well, it just makes our life easier.
>
> Pike, we (Sunbird/Lightning team) have a release coming up, that is at
> least as important to us as Firefox 2 is important for you and the
> Mozilla Corporation.
>
> And since we'd like to tag the /l10n repository on October 03 for the 1.8
> branch (from which we'll release Lightning, Sunbird will come from its
> own branch which originates from the 2006-09-27 trunk), this is really a
> major showstopper for us.
>
> I understand your desire to keep everything nice and tidy, but I fail to
> see how checkins to /l10n/ab-CD/calendar could somehow affect FF2.
>
> Therefore I would really appreciate it, if you could revise your
> statement above.
>

We have 40 localizations to ship, and we need to lock them down. There
are three parts to this, one is, we have to lock down all of them at
once. Everything else is just technically not feasible. The next one is
to send out the message of the lockdown, and this is in part a tooling
problem. We just don't have one tinderbox for l10n, where we could post
a tree rules message. I post that to the main l10n tinderbox, but that's
of very limited use to localizers, so that message is partly cosmetic.
Nor do all localization teams follow the posts in .l10n as eagerly as we
would hope, or just don't get the real life implications of what is
written. The third part is to actually watch that that happens. Sadly,
bonsai-l10n sucks at that. Both because it doesn't show branch-only
check-ins, and because there's no way to reasonably filter.

Unfortunately, folks do see other check-ins, and then interpret the
stuff they see in a way that makes it close to impossible to freeze just
parts of the l10n rep. At least not if you really want it frozen. The
fact that all our products depend on common parts doesn't help.

Thus, when it comes down to it, I need to freeze the complete branch for
a Firefox release. At least as long as we're evaluating which version on
that branch to build. The scheme of freezing the tree and then picking
some not-so-bad timestamp between a bunch of accidental and
non-accidental non-approved check-ins to tag l10n is just not working right.

I'm sorry if our problems to actually get Firefox RC2 built have a
negative impact on the Calendar release, but I don't see a way around that.

Axel

Axel Hecht

unread,
Oct 1, 2006, 5:22:54 PM10/1/06
to
Hi all,

schrep is OK with it, so we're reopening the MOZILLA_1_8_BRANCH for
check-ins that affect Thunderbird or Calendar only, by source location.

Firefox and Toolkit remain locked down.

Thank you for your cooperation

Axel

Dan Mosedale

unread,
Oct 1, 2006, 5:46:42 PM10/1/06
to
[Followup-To: set to mozilla.dev.planning only]

Axel Hecht wrote:
> schrep is OK with it, so we're reopening the MOZILLA_1_8_BRANCH for
> check-ins that affect Thunderbird or Calendar only, by source location.

Thanks for your willingness to be flexible about all this stuff.

Dan

0 new messages