Closed
Bug 368244
Opened 18 years ago
Closed 17 years ago
Create a scheme to finalize set of shipped locales
Categories
(Release Engineering :: General, defect, P3)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 415895
People
(Reporter: Pike, Unassigned)
Details
Currently, we have a shipped-locales file, which is used to create the release builds. Then we test the release builds and evaluate if we can ship them. Then we may end up having to change shipped-locales.
We should have a clear position in the release schedule when we determine the locales we ship, and find out how to make the process up to that point as flexible as possible, and the process after that as failsafe as possible.
Questions affected include:
- which part of the repository is tagged with a particular release tag? (build)
- for which locales to we generate candidates? (build)
- which questions do we need to get answered when to make the call? (build/qa)
More?
Updated•18 years ago
|
Assignee: nobody → build
Component: Build Config → Build & Release
Product: Toolkit → mozilla.org
QA Contact: build-config → preed
Version: unspecified → other
Updated•18 years ago
|
Priority: -- → P3
Updated•17 years ago
|
Assignee: build → nobody
QA Contact: mozpreed → build
Comment 1•17 years ago
|
||
Anything here not covered by bug 415895?
Updated•17 years ago
|
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•