All users were logged out of Bugzilla on October 13th, 2018

Deploy locale-aware bouncer to production

RESOLVED INVALID

Status

RESOLVED INVALID
9 years ago
9 years ago

People

(Reporter: wenzel, Unassigned)

Tracking

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
Bouncer trunk is aware of locales now and we should use that in production.

Dave: What needs to happen to deploy this?

Here's what I figured out so far: There are SQL changes in bug 395232, and there is a set of initial locales in 395237 (which might be out-of-date, probably need to re-feed this from locale-details?).

Furthermore, to compensate for the "language hack" that used to just replace en-US with the locale a user asked for, we need to add all missing locale entries to the database: bug 408674. When adding new locations to bouncer, Build will need to do so for each locale, there is a quick-add option on trunk (bug 395237), but there's no command-line script yet (bug 408674).
(Reporter)

Comment 1

9 years ago
morgamic: I just noticed, languages are a separate table which is joined in -- that won't help our mission to reduce the amount of JOINs. Also, it does not use localeDetails yet. Do I need to block this bug and make it use localeDetails instead? This will have the same problem as bug 398366 comment 10: bouncer needs to be svn upped when locales change (though that happens more rarely than product releases).
(Reporter)

Updated

9 years ago
Blocks: 457614
(Reporter)

Comment 2

9 years ago
Will make a new bug for landing tuxedo soon.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.