please follow up to this thread to opt in for Beta 1.
We're string frozen since Thursday, and code freeze is Sept 30th at
11:59pm PDT.
An extra would be if you could provide a link to hg.m.o referencing the
changeset you want to get in.
This release is a bit new, and is likely going to be done by hand by the
release team.
Sorry for the late announcement, I have issues with my connectivity in
my home office.
Release criteria are green on tinderbox and l10n dashboard.
Seth is looking into QA ideas for B2 and RCs.
Axel
fr locale is opting in, patchset a7c003554f46
--
wladow
hu locale is opting in, patchset 279d4db75211
ru locale is opting in, patchset a86d6547da37
--
Sincerely yours,
Alexander L. Slovesnik a.k.a. Unghost
==>Web-page: http://www.unghost.ru/
==>Jabber ID: ung...@mozilla-russia.org
==>Gmail Talk ID: ung...@gmail.com
==>IRC: irc://irc.mozilla.org/mozilla-ru
At the very last moment:
http://hg.mozilla.org/l10n-central/es-ES/rev/684b7eb7ecc8
I'm talking on behalf of Guillermo López, which has had a HW failure
(well, his laptop). ;-) es-ES opts in.
Ricardo
>
> Hi all,
>
> please follow up to this thread to opt in for Beta 1.
>
> We're string frozen since Thursday, and code freeze is Sept 30th at
> 11:59pm PDT.
>
> An extra would be if you could provide a link to hg.m.o referencing the
> changeset you want to get in.
>
Irish (ga-IE) would like to opt in for b1.
http://hg.mozilla.org/l10n-central/ga-IE/rev/097b91291d3f
Kevin
Romi
Thanks.
pt-BR opts in.
http://hg.mozilla.org/l10n-central/pt-BR/rev/a6376e4c62f6
--
Jeferson
Changeset aa3a55a987e7
http://hg.mozilla.org/l10n-central/it/file/aa3a55a987e7
Francesco
fy-NL locale is opting in, patchset f56da923da65
Kind regards,
--
Wim
fryske...@gmail.com
www.mozilla-nl.org/ <http://www.mozilla-nl.org/projecten/frysk>
www.mozbrowser.nl <http://www.mozbrowser.nl/forum/viewforum.php?f=38>
www.fryskesoftware.nl <http://www.fryskesoftware.nl>
RQ
http://hg.mozilla.org/l10n-central/zh-CN/5d7295a2e778
> _______________________________________________
> dev-l10n mailing list
> dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-l10n
>
Thanks.
[ca] opting in.
Last changeset:
http://hg.mozilla.org/l10n-central/ca/rev/ec1fec4515bd
- --
Toni Hermoso Pulido
http://www.cau.cat
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFI4er63O471rZ7Q9wRAgmsAJsFyW3im5VKcNPPJ4jcXLd0n41BBACfYLTy
BAebmStVXwq0FM/YmWolQM0=
=VHYr
-----END PGP SIGNATURE-----
>
pa is ready with changeset: c712d30e06bb
thanks
A S Alam
Changeset d5c995c178f3
Best regards,
João Miguel Neves
Axel Hecht escreveu:
> _______________________________________________
> dev-l10n mailing list
> dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-l10n
>
--
Intraneia
http://www.intraneia.com/
Suporte a Software Livre
Tradução/Localização de software e sítios web
Desenvolvimento de software
Ao seu serviço...
Changeset
http://hg.mozilla.org/l10n-central/ja/rev/d3e357c1d1ee
and
http://hg.mozilla.org/l10n-central/ja-JP-mac/rev/c0977b38f38c
Thanks.
Eduardo, that build has missing strings,
http://l10n.mozilla.org/buildbot/compare/hg-langpack/2497.
Axel
We have been notified of a translation error at:
Instead of "...ventana ventana" it should be "...ventana nueva".
Can we fix it now and notify the new changeset or should we better
wait until the B1 cut has been done?
TIA
If you get the changeset into my queue, you're fine, but I wouldn't fall
over if I missed out on this.
We're not freezing the l10n repos anyway, so you can land, and we'll tag
and release with the given changesets.
Actually, make that "I guess" on the not-freezing part. I don't know if
we'll have to for the tagging/branching part.
Axel
-ville/mozilla.fi
Hi, Axel.
Ukrainian (uk) is opting in.
http://l10n.mozilla.org/buildbot/compare/hg-langpack/2556
http://hg.mozilla.org/l10n-central/uk/file/939ec7335354
OK, thanks. Done:
http://hg.mozilla.org/l10n-central/es-ES/rev/9533e3cca6a1
> We're not freezing the l10n repos anyway, so you can land, and we'll tag
> and release with the given changesets.
>
> Actually, make that "I guess" on the not-freezing part. I don't know if
> we'll have to for the tagging/branching part.
I hope to be on time. :-)
Ricardo.
sv-SE opts in.
Changeset: 31f6caf6c4e4
--
Hasse
sv-SE l10n team
Fixed. Sorry, I was doing compare-locales with another version.
Kurdish (ku) would like to opt in. Sorry, no changeset yet.
(Substituting for Marcoos - he is offline)
--
Hubert Gajewski
Aviary.pl
http://www.aviary.pl
opting in for "de" with last changeset being faa4b56cd096
--Kadir
Thanks
Danishka
plese add cs in beta1 - revision 94910d2d45ec
Pavel Franc
Hi Erdal,
so far, Kurdish is still red, see
http://l10n.mozilla.org/buildbot/compare/hg-langpack/2519 for the latest
comparison.
As we had that before, do you do an
hg pull -u
to update en-US? And did you push you local check-ins?
Axel
e.g. We just finished Fx 3.0.2 translations one month before I guess and
now Fx 3.1 is in the queue.
It becomes really difficult for localizers to keep the translations
up2date, who work on various other localization projects, like Gnome,
KDE, XFCE, Fedora, etc and especially when communities are very small in
size.
This confuses me to understand the importance of Fx 3.0.x and Fx 3.x at
times!
--
Regards,
Ankit Patel
http://www.indianoss.org/
> I don\'t understand, why do we have such quick releases immediately
> after the other.
>
> e.g. We just finished Fx 3.0.2 translations one month before I
> guess and now Fx 3.1 is in the queue.
>
> It becomes really difficult for localizers to keep the translations
> up2date, who work on various other localization projects, like Gnome,
> KDE, XFCE, Fedora, etc and especially when communities are very small
> in size.
>
> This confuses me to understand the importance of Fx 3.0.x and
> Fx 3.x at times!
Ankit, a few general thoughts first:
- Localization is always driven by development speed. If a certain
product is in a fast development cycle, this has implications for
the localization teams of course.
- Fx 3.0.x was the big release which incorporated all the work since
the Fx 2.0.x release nearly two years earlier. Fx 3.1 will be a much
smaller release, with a much lower l10n footprint, meaning the
number of changes between Fx2 and Fx3 were much larger than the
string changes between Fx3 and Fx31 will be.
A few more specific thoughts:
- The Fx3 release is now three months behind us. I understand that
you only catched up with the 3.0.2 release, but IMO you should
put this more into the perspective of when Fx3 was released and
how long ago that was and not look at it from the perspective of
when you were able to catch up.
- Do you understand that this will be the first *beta* of Fx31?
This will not be the finished product. The final release of Fx31
is currently planned for early February 2009 as far as I know. So
if you aren\'t able to make it now, you could still shoot for the
Fx31 final release or for the second beta, which will probably
come out somewhere in November or December this year.
I hope that helps
Simon
--
Thunderbird/Calendar Localization (L10n) Coordinator
Calendar website maintainer: http://www.mozilla.org/projects/calendar
Calendar developer blog: http://weblogs.mozillazine.org/calendar
Do we have any schedule/roadmap/milestones page for Firefox x.x upcoming
releases? So, that I can do the scheduling of all localization projects
I handle.
author Rajesh Ranjan <rajes...@yahoo.com>
Wed Oct 01 17:46:53 2008 +0530 (at Wed Oct 01 17:46:53 2008 +0530)
changeset 14 faae828cacee
regards,
--------------
Rajesh Ranjan
Kramashah
----- Original Message ----
From: Axel Hecht <l1...@mozilla.com>
To: dev-...@lists.mozilla.org
Sent: Tuesday, September 30, 2008 12:32:48 AM
Subject: [ANNOUNCE] Firefox 3.1 Beta 1 Opt in Thread
Hi all,
please follow up to this thread to opt in for Beta 1.
We're string frozen since Thursday, and code freeze is Sept 30th at
11:59pm PDT.
An extra would be if you could provide a link to hg.m.o referencing the
changeset you want to get in.
This release is a bit new, and is likely going to be done by hand by the
release team.
Sorry for the late announcement, I have issues with my connectivity in
my home office.
Release criteria are green on tinderbox and l10n dashboard.
Seth is looking into QA ideas for B2 and RCs.
Axel
http://hg.mozilla.org/l10n-central/he/rev/818a5ad594ab
On Sep 30, 12:06 pm, "Tomer Cohen - mozilla.org.il" <tom...@gmail.com>
wrote:
> Hebrew is ready to opt-in. Changeset 4f008d419edb.
>
> Thanks.
ko lately opt-in change set 325fbd3255b5
Thanks.
Channy
Hi Channy,
sadly, the Korean builds are still red. Both on
http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n-ko and on
http://l10n.mozilla.org/buildbot/waterfall, with the latest comparison
run being http://l10n.mozilla.org/buildbot/compare/hg-langpack/2589.
I had to kick my master to pick up changes again, sadly, should be fine
for now again.
Axel
Signed, sealed, delivered.
https://bugzilla.mozilla.org/show_bug.cgi?id=458056 has the final
patches with the localizations for Beta 1.
We're having 36 languages on, including en-US, not counting ja-JP-mac.
That is a great achievement, given that this is the first release from
hg we're doing.
I would like to thank all of you for doing the additional step with
specifying the changeset, that's a good addition in getting to a
reliable release process.
Thanks, and onwards to Beta 2.
As I indicated, we'll need a short window of closing the repositories
during the branching and tagging. I'll make sure there's a post in this
group for that.
Axel
http://hg.mozilla.org/l10n-central/zh-CN/rev/2e463ab52bc3
On Tue, Sep 30, 2008 at 3:11 PM, 文少华 <shaoh...@gmail.com> wrote:
> zh-CN opt in
>
> http://hg.mozilla.org/l10n-central/zh-CN/5d7295a2e778
>
>
>
> On Tue, Sep 30, 2008 at 3:02 AM, Axel Hecht <l1...@mozilla.com> wrote:
>
>> Hi all,
>>
>> please follow up to this thread to opt in for Beta 1.
>>
>> We're string frozen since Thursday, and code freeze is Sept 30th at
>> 11:59pm PDT.
>>
>> An extra would be if you could provide a link to hg.m.o referencing the
>> changeset you want to get in.
>>
>> This release is a bit new, and is likely going to be done by hand by the
>> release team.
>>
>> Sorry for the late announcement, I have issues with my connectivity in
>> my home office.
>>
>> Release criteria are green on tinderbox and l10n dashboard.
>>
>> Seth is looking into QA ideas for B2 and RCs.
>>
>> Axel