I have noticed that some locales have a green Sunbird tinderbox on the
trunk, but an orange one on MOZILLA_1_8_BRANCH, namely eu, nb-NO and sk.
Therefore I just wanted to remind you, that Calendar has a strict
cross-commit policy in place, meaning that the trunk and the 1.8 branch
stay in sync as much as possible.
This is especially true for all strings, which are *exactly the same* on
both trunk and 1.8 branch. Therefore I ask you to please commit your
changes to Calendar strings always to both trees (trunk and 1.8 branch).
This will result in green tinderboxen on both trunk and 1.8 branch and
will also broaden your testing community as our builds from the
1.8 branch (0.8pre) are more stable than the trunk builds (0.6a1).
If you have any questions, please let me know here in the newsgroup.
Thanks
Simon
--
Calendar l10n coordinator
Calendar Website Maintainer: http://www.mozilla.org/projects/calendar
Calendar developer blog: http://weblogs.mozillazine.org/calendar
0.7 is already released. Calendar development continues on Trunk and
MOZILLA_1_8_BRANCH. Files in mozilla/calendar/locales are identical
on Trunk and Branch. (Or should be).
> Is MOZILLA_1_8_BRANCH open?
See <http://tinderbox.mozilla.org/Mozilla1.8-l10n/> for tree rules
and status. For calendar only checkins you don't need approval. For
toolkit, browser, mail etc. checkins you need to request approval first.
es-ES is very much in the opposite situation. I commit only to
MOZILLA_1_8_BRANCH because I don't use the .mk scripts in the tree,
but some bash scripts (I really like/need a previous diff before
checking out, and we split our work so toolkit is just a different
product in terms of L10n maintenance).
That means that cross-commit is not very convenient for me (I have to
do it manually), and I understand that there will not be official
Calendar releases from trunk as long as Thunderbird 3 is not released
or close to it, so I just keep MOZILLA_1_8_BRANCH in sync. Does that
pose a big problem for Calendar project?
TIA
--
If it's true that we are here to help others,
then what exactly are the OTHERS here for?
>> I have noticed that some locales have a green Sunbird tinderbox on the
>> trunk, but an orange one on MOZILLA_1_8_BRANCH, namely eu, nb-NO and sk.
>>
>> Therefore I just wanted to remind you, that Calendar has a strict
>> cross-commit policy in place, meaning that the trunk and the 1.8 branch
>> stay in sync as much as possible.
>>
>> This is especially true for all strings, which are *exactly the same* on
>> both trunk and 1.8 branch. Therefore I ask you to please commit your
>> changes to Calendar strings always to both trees (trunk and 1.8 branch).
>
>es-ES is very much in the opposite situation. I commit only to
>MOZILLA_1_8_BRANCH because I don't use the .mk scripts in the tree,
>but some bash scripts (I really like/need a previous diff before
>checking out, and we split our work so toolkit is just a different
>product in terms of L10n maintenance).
>
>That means that cross-commit is not very convenient for me (I have to
>do it manually), and I understand that there will not be official
>Calendar releases from trunk as long as Thunderbird 3 is not released
>or close to it, so I just keep MOZILLA_1_8_BRANCH in sync. Does that
>pose a big problem for Calendar project?
No it doesn't. If it's not convenient for you to keep the trunk
up-to-date then don't. My post was just meant a s a friendly reminder,
nothing more.
Thanks for your ongoing support!
Sorry,
The basque (eu) tinderbox on MOZILLA_1_8_BRANCH is now green, sorry I
forgot commit changes in this branch but now is in sync with trunk.
Thanks by the advice
Hi, we (sk team) know about this, dont worry. Mozilla_1_8_BRANCH will go
green soon. We are using trunk builds for all products for testing
purposes, so for initial testing we use 0.6a1 as it is the same as you
said. When we are closer to release date, 1.8 branch builds are ever
used for testing of course.
--
wladow
Mozilla.sk admin
>> I have noticed that some locales have a green Sunbird tinderbox on
>> the trunk, but an orange one on MOZILLA_1_8_BRANCH, namely eu, nb-NO
>> and sk.
>>
>> Therefore I just wanted to remind you, that Calendar has a strict
>> cross-commit policy in place, meaning that the trunk and the 1.8
>> branch stay in sync as much as possible.
>
> Hi, we (sk team) know about this, dont worry. Mozilla_1_8_BRANCH will
> go green soon. We are using trunk builds for all products for testing
> purposes, so for initial testing we use 0.6a1 as it is the same as you
> said. When we are closer to release date, 1.8 branch builds are ever
> used for testing of course.
Hi wladow,
thanks for your reply and the explanation. I wasn't sure, whether you
were still aware of the cross-commit policy, hence the original post.
Thanks for clearing things up.
Cya
> This is especially true for all strings, which are *exactly the same* on
> both trunk and 1.8 branch. Therefore I ask you to please commit your
> changes toCalendarstrings always to both trees (trunk and 1.8 branch).
Hello. I noticed that there is a property in Branch that does not
belong to Branch:
Properties in ./calendar/installer/custom.properties don't match:
In trunk: (remove these from your localization)
REG_APP_DESC
What does your policy say about this one?
> Hello. I noticed that there is a property in Branch that does not
> belong to Branch:
>
> Properties in ./calendar/installer/custom.properties don't match:
> In trunk: (remove these from your localization)
> REG_APP_DESC
>
> What does your policy say about this one?
See Bug 368865
<https://bugzilla.mozilla.org/show_bug.cgi?id=368865>
/Stefan