Re: Allowing a few check-ins to CVS trunk in preparation for 3.0.1 or a possible RC2
Axel Hecht
> Hello All!
>
> This is Sarves from Sri Lanka and we are working on Firefox
> localization since Firefox 2.0.
> Our ta-LK language xpi is available in AMO public. Around 2000
> downloads, but still we didn't get any complains.
>
> We also put that into the Bugzilla.
> We would like to commit our localization and I have been requesting
> for ta-LK locale, but still I didn't get any reply.
> What should we do? how we can commit our pack... We would like to see
> ta-LK with Firefox 3.
>
> Hope someone in this group may help on this..
Hi Sarves,
sorry for the lag. We're still busy with the existing locales being in
the endgame for Firefox 3.0.
Those locales that we're shipping partly went through really rough
waters, due to us sending contradicting messages and docs being
confusing or wrong.
The not-so-good answer to your question is, I don't have a satisfying
answer for what it takes for you to ship on Firefox 3. Like, I can tell
you that web services review and in-product pages are missing at least,
but turning that into a statement that makes sense for new locales is
pending. Most locales that are now up to ship in Firefox 3.0 are
shipping Beta releases for up to half a year, and we're going back and
forth over search engines and protocol handlers with some of them still.
I bet that that's not the process you want to join.
We're currently working on fixing that, but as most of the team is
flooded, that doesn't go as quickly as we'd love to.
The same apology goes out to the other locales in the queue, and of
course to those that went through the back-and-forth.
Hope that makes sense
Axel
Axel Hecht
on a different note on this thread, I started to land the l10n patches
in preparation for RC2 or 3.0.1.
This doesn't say yet whether we'll have an RC2 or not.
I'm checking those in so that we actually know that the patches that get
approved get landed in time, RC2 will be on a rather hectic timeline, if
we do it.
If you're the author of one of those patches or collaborator, please
update your working copy and resolve any conflicts, if there were.
That's important to do so that we're working on the same state of the
tree again.
HTH
Axel
Brian King
It's unclear what patches you are referring to ... could you please
clarify if they affect all locales and provide some linkage that might help.
Thanks,
- Brian
> _______________________________________________
> dev-l10n mailing list
> dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-l10n
Axel Hecht
I'm going over bug that request approval1.9 on patches, and if I land
them, I update their whiteboard status so that they come up in the
rc2-fixed bugs.
People should get bugmail when they're affected, as those are bugs in
their components, mostly they've been requesting approval themselves.
Clearer?
Axel
Damjan Georgievski
> in preparation for RC2 or 3.0.1.
cool that there might be RC2 or 3.0.1 with l10n updates... :)
> This doesn't say yet whether we'll have an RC2 or not.
I really hope so, if not but because of
https://bugzilla.mozilla.org/show_bug.cgi?id=411831
> I'm checking those in so that we actually know that the patches that get
> approved get landed in time, RC2 will be on a rather hectic timeline, if
> we do it.
I'll also send a patch for
security/manager/chrome/pipnss/pipnss.properties
In a really stupid overlook (because the comments in the original file were
lost) we didn't notice there's a limit to the byte lenght of the strings
there.
https://bugzilla.mozilla.org/show_bug.cgi?id=435789
ps.
Axel is it possible to have some kind of a test for these special kind of
strings?
--
damjan
Axel Hecht
>> on a different note on this thread, I started to land the l10n patches
>> in preparation for RC2 or 3.0.1.
>
> cool that there might be RC2 or 3.0.1 with l10n updates... :)
>
>> This doesn't say yet whether we'll have an RC2 or not.
>
> I really hope so, if not but because of
> https://bugzilla.mozilla.org/show_bug.cgi?id=411831
>
>> I'm checking those in so that we actually know that the patches that get
>> approved get landed in time, RC2 will be on a rather hectic timeline, if
>> we do it.
>
> I'll also send a patch for
> security/manager/chrome/pipnss/pipnss.properties
>
> In a really stupid overlook (because the comments in the original file were
> lost) we didn't notice there's a limit to the byte lenght of the strings
> there.
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=435789
>
I'll look into these tomorrow.
>
> ps.
> Axel is it possible to have some kind of a test for these special kind of
> strings?
>
Sure, write one ;-). I have a bunch of ad-hoc tests locally myself,
shouldn't be too hard to hack them up. Getting them built is a bit
trickier, no idea how to do that yet.
Axel