Comments on: Triggering l10n builds http://blog.mozilla.com/axel/2009/02/24/triggering-l10n-builds/ Free your mind and your ass will follow. Tue, 07 Feb 2012 10:14:33 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Axel Hecht http://blog.mozilla.com/axel/2009/02/24/triggering-l10n-builds/comment-page-1/#comment-1481 Axel Hecht Wed, 25 Feb 2009 00:18:55 +0000 http://blog.mozilla.com/axel/?p=131#comment-1481 The comparison would be en-US source default head vs l10n source default head. The comparison would be en-US source default head vs l10n source default head.

]]> By: sethb http://blog.mozilla.com/axel/2009/02/24/triggering-l10n-builds/comment-page-1/#comment-1480 sethb Wed, 25 Feb 2009 00:14:33 +0000 http://blog.mozilla.com/axel/?p=131#comment-1480 "ut as you can see from the waterfall (there is some good in waterfalls, lastly), the en-US builds are far from done so far. That’s why the l10n builds have compareOnly set. These builds should merely run compare-locales and report the current string work on the dashboard, and be done with it." so, with the compareOnly set that is triggered with a new en-us build, you only get a compare-locales. against what, exactly? the old, pre-new-en-US build? “ut as you can see from the waterfall (there is some good in waterfalls, lastly), the en-US builds are far from done so far. That’s why the l10n builds have compareOnly set. These builds should merely run compare-locales and report the current string work on the dashboard, and be done with it.”

so, with the compareOnly set that is triggered with a new en-us build, you only get a compare-locales. against what, exactly? the old, pre-new-en-US build?

]]>