Opening l10n repository on MOZILLA_1_8_BRANCH for approved check-ins
Axel Hecht
we're opening up the l10n repository for approved check-ins.
The rules for Thunderbird and Calendar specific changes remain as is for
now, though I expect changes there soon.
Please make sure that any change on the MOZILLA_1_8_BRANCH has a bug
filed in bugzilla, likely in the component for your locale.
All check-ins changing the MOZILLA_1_8_BRANCH (affecting Firefox) should
mention their bug, describe the change, and who approved the change,
something like
"bug 12345, fix typos and resize prefwindow, a=l10n".
For those locales that already shipped, please attach patches [1] and
request approval1.8.1.1 by setting that flag to '?'.
For those locales that haven't shipped, make sure that there is a bug
filed to track your changes, too. I won't require patches for the large
catch-up changes, as I'll hardly read them anyway. Just comment in the
bug what you'll do, and I'll approve that with a comment. Once the
initial landing is done, please follow the procedure set out for shipped
locales.
This includes branches and merges.
For those locales that need to branch their current trunk to get it on
MOZILLA_1_8_BRANCH, either poke me to do that, or, if you're familiar
with CVS, tag your tree with MOZILLA_1_8_BASE and then branch to
MOZILLA_1_8_BRANCH. The base tag will make it easier to merge in the
future. If you're going to do it yourself, please poke me in a bug to
get approval for that.
http://ximbiot.com/cvs/wiki/index.php?title=CVS--Concurrent_Versions_System_v1.12.12.1:_Revisions#Tags-Symbolic_revisions
and
http://ximbiot.com/cvs/wiki/index.php?title=CVS--Concurrent_Versions_System_v1.12.12.1:_Branching_and_merging
are the sections in the cvs docs you should have understood to branch
yourself. Make sure to be in your own locale directory when doing this,
that is, in the right subdirectory of l10n/. Branching and tagging wrong
does break things, and may be at least awful to undo.
For those locales that shipped, you may want to merge your work back to
trunk. Not all locales did that yet. If you do, you want to tag your
current state on the branch. If you need help with that, poke me.
If you have questions or unsure, poke me, in particular when it comes
down to merges and branches.
Axel
[1] cvs -z3 diff -u
is the right way to do those. I just found out that MDC suggests a
contextsize of 8 at
http://developer.mozilla.org/en/docs/Creating_a_patch, but that's just
confusing for l10n patches.
Ricardo Palomares Martinez
> we're opening up the l10n repository for approved check-ins.
> The rules for Thunderbird and Calendar specific changes remain as is for
> now, though I expect changes there soon.
>
> Please make sure that any change on the MOZILLA_1_8_BRANCH has a bug
> filed in bugzilla, likely in the component for your locale.
>
> All check-ins changing the MOZILLA_1_8_BRANCH (affecting Firefox) should
> mention their bug, describe the change, and who approved the change,
I was about to commit some changes affecting Thunderbird (honestly, I
thought l10n TB was already frozen, I almost miss it), but re-reading
your message I find some contradictory statements, so I better ask:
should I file a bug to check-in new and updated strings affecting
_only_ Thunderbird (no Firefox nor toolkit involved, of course)?
I ask because you first say that rules for Thunderbird specific
changes remain the same, just next you say that every change in
MOZILLA_1_8_BRANCH has a bug filed, and finally you say that changes
in MOZILLA_1_8_BRANCH (affecting Firefox) need the bug mentioned in
the check-in message. Should I take this as 2-1 in favour of only
Firefox check-ins need bug and approval? :-)
> For those locales that shipped, you may want to merge your work back to
> trunk. Not all locales did that yet. If you do, you want to tag your
> current state on the branch. If you need help with that, poke me.
Using MozillaTranslator I feel that it will be simpler for me just to
update from current 2.0 glossary to current trunk, review and
translate everything needed and export and commit all files at once
(this will also add licenses not present in current trunk
translation). Will that pose any problem for you or Mozilla Foundation?
TIA
--
If it's true that we are here to help others,
then what exactly are the OTHERS here for?
Roberto Pincipiano
> Axel Hecht escribió:
>> The rules for Thunderbird and Calendar specific changes remain as is for
>> now, though I expect changes there soon.
>
> I was about to commit some changes affecting Thunderbird (honestly, I
> thought l10n TB was already frozen, I almost miss it), but re-reading
> your message I find some contradictory statements, so I better ask:
> should I file a bug to check-in new and updated strings affecting
> _only_ Thunderbird (no Firefox nor toolkit involved, of course)?
>
Being TB l10n open I interpreted the above sentence as "it remais open"
and I've continued doing checkins. Can you pls clarify Axel?
(closing TB while english strings still changing should not be a good
idea I think).
Roberto
Axel Hecht
Yes, thunderbird- and calendar-only changes are OK still.
Axel
Axel Hecht
> Hi,
>
> we're opening up the l10n repository for approved check-ins.
> The rules for Thunderbird and Calendar specific changes remain as is for
> now, though I expect changes there soon.
>
> Please make sure that any change on the MOZILLA_1_8_BRANCH has a bug
> filed in bugzilla, likely in the component for your locale.
>
> All check-ins changing the MOZILLA_1_8_BRANCH (affecting Firefox) should
> mention their bug, describe the change, and who approved the change,
> something like
> "bug 12345, fix typos and resize prefwindow, a=l10n".
Guess the first line above hasn't been clear: All check-ins affecting
Firefox ...
For all those that have been waiting on approvals, I didn't have
permissions to set those flags yet, and I'm not on a good connection
today, so I'll take another peek tomorrow afternoon.
Axel