Closed Bug 537280 Opened 16 years ago Closed 15 years ago

Change decision making for which list of locales is generated per platform (nightly repackages)

Categories

(Release Engineering :: General, defect, P3)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: armenzg, Unassigned)

Details

In bug 531275 we want to only generate wince repackages for the locale 'id'. To address this I added this piece of code >+ locales = None >+ if platform is 'wince': >+ locales = {'id':[]} but that should not be decided last second but to defined in a configuration file. I thought of doing: BRANCHES['mozilla-1.9.2']['l10n_platforms'] = { 'linux': None, 'macosx': None, 'win32': None, 'wince': {'id':[]}, } but thought that it is better if we do it similar to releases where a json file is used and makes things more clear. Let's see what the best solution is since we have l10n configuration information spread across too many places.
sorry, but the idea that we just want Indonesian is broken. I think that was just an example and triggered the request, but shipping Firefox for just one language is not happening.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WONTFIX
(In reply to comment #1) > sorry, but the idea that we just want Indonesian is broken. I think that was > just an example and triggered the request, but shipping Firefox for just one > language is not happening. > If you want more than 'id' for WinCE we should discuss it on the dependent bug. I want to keep this bug for the ability to regulate which locales get build in which branch and for which platforms. Currently we can only say "all" locales or none.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
For nightlies, we want all locales. I consider this bug to be FIXED, in particular for nightlies.
Component: Release Engineering → Release Engineering: Future
Mass move of bugs from Release Engineering:Future -> Release Engineering. See http://coop.deadsquid.com/2010/02/kiss-the-future-goodbye/ for more details.
Component: Release Engineering: Future → Release Engineering
Priority: -- → P3
Status: REOPENED → RESOLVED
Closed: 16 years ago15 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.