Latest 1.6
Giacomo Magnini
locale tag used is still 1.6b. If you use a locale xpi with version tag
1.6, you'll end up with a (needs update) comment alongside the translation.
I thought locale versions were supposedly fixed with milestone.txt
stuff, am I wrong?
Cheers, Giacomo.
KaiRo - Robert Kaiser
We now are using the version strings from chrome-versions.sh
<http://lxr.mozilla.org/mozilla/source/config/chrome-versions.sh> for
that, and in the 1.6 branch they remained unchanged to 1.6 Beta.
I think we have a bunch of differences from 1.6b to 1.6, so it might be
good to change it. In the future, when the string freeze at beta really
should hold, it's the idea that we don't need to change it here, and we
can ship the same langauge packe for beta and final (well, we'll
probably want to make some bug fixes in the localizations though...)
If we want it to change, we should request that soon.
Greetings from Vienna,
Robert Kaiser
Giacomo Magnini
> I think we have a bunch of differences from 1.6b to 1.6, so it might be
> good to change it. In the future, when the string freeze at beta really
> should hold, it's the idea that we don't need to change it here, and we
> can ship the same langauge packe for beta and final (well, we'll
> probably want to make some bug fixes in the localizations though...)
Well, there are at least 10-20 strings changed between 1.6b and 1.6, and
there is a bug with a late-l10n keyword set, so I guess this change is
really needed.
> If we want it to change, we should request that soon.
Maybe it would be advisable to add a comment to the bug i was referring
to above. Don't have the bug number handy, but will find out soon.
> Greetings from Vienna,
Greetings from Rome, caput mundi! :)
Cheers, Giacomo.
KaiRo - Robert Kaiser
> there is a bug with a late-l10n keyword set, so I guess this change is
> really needed.
I'd second you.
>> If we want it to change, we should request that soon.
>
> Maybe it would be advisable to add a comment to the bug i was referring
> to above. Don't have the bug number handy, but will find out soon.
Nah. That bug is _not_ marked blocking1.6+ and was moved to 1.7 - if we
want it, we have to be fast and file a new bug and request blocking1.6?
quite soon, would be best if it happened last week ;-)
Robert Kaiser
Giacomo Magnini
> Nah. That bug is _not_ marked blocking1.6+ and was moved to 1.7 - if we
> want it, we have to be fast and file a new bug and request blocking1.6?
> quite soon, would be best if it happened last week ;-)
I've just seen the change in the flags. Would you mind filing the bug
for the string version change, or should I do it myself? :)
Cheers, Giacomo.
KaiRo - Robert Kaiser
> I've just seen the change in the flags. Would you mind filing the bug
> for the string version change, or should I do it myself? :)
I think it would be best if you do it (and quite fast as they plan to
release 1.6 on monday or tuesday) and CC ka...@kairo.at on the bug.
Thanks,
Robert Kaiser
KaiRo - Robert Kaiser
Giacomo Magnini
> http://bugzilla.mozilla.org/show_bug.cgi?id=230621
Thanks for the pointer. I've added a comment, and I didn't file it
sooner since I was cut off the Net since this early morning.
This helped alot with the italian version of the Mozilla help guide... :)
Cheers, Giacomo.
KaiRo - Robert Kaiser
>
>
> Thanks for the pointer. I've added a comment, and I didn't file it
> sooner since I was cut off the Net since this early morning.
> This helped alot with the italian version of the Mozilla help guide... :)
OK, seems it's changed already and the bug is fixed. Just wanted to note
it here so everybody can read it.
localeVersion for Mozilla 1.6 is now 1.6 - as we would expect it :)
Robert Kaiser