Closed Bug 518359 Opened 15 years ago Closed 15 years ago

use alternative mozconfigs for L10n from release automation

Categories

(Release Engineering :: General, defect, P3)

Product:
Release Engineering
Component:
General
Platform:
x86
macOS
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 482447

People

(Reporter: armenzg, Unassigned)

References

Details

(Whiteboard: [l10n])

In bug 517544 we had to fix that we now needed to make memory/jemalloc. This is due that we use mozconfigs in our release automation but not on our nightly runs. To avoid situations like this we want to switch to mozconfig files for l10n. The problem is that we will have to maintain another set of mozconfigs aside of the currently existent ones. Suggestions welcomed to avoid this extra thing to remember when writing patches for a new release.
Whiteboard: [l10n]
Priority: -- → P3
Putting into the future list since I won't be able to look at it for at least the next 2 weeks. I will grab it if nobody does before I do.
Assignee: armenzg → nobody
Component: Release Engineering → Release Engineering: Future
Depends on: 531275
Blocks: 537287
No longer blocks: 537287
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Moving closed Future bugs into Release Engineering in preparation for removing the Future component.
Component: Release Engineering: Future → Release Engineering
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.