Closed
Bug 449828
Opened 16 years ago
Closed 15 years ago
Produce updates for l10n nightly builds
Categories
(Release Engineering :: General, defect, P2)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: joduinn, Assigned: coop)
References
Details
(Whiteboard: [l10n])
We've never produced nightly updates for l10n before, on cvs or on hg. Until now, localizers manually download new builds as/when they can.
This is something we think we can do, after some of the other l10n cleanup work is completed. After the summit, we *know* the localizers will like it, because they said so!! :-)
Before we can do this, we need to know we're producing better quality nightly repacks. It would be bad for someone who is on a working l10n nightly build to be automatically updated to a known-broken l10n build the next night.
Some requirements are:
- dont produce an l10n build with missing entities. For newly added entities that are missing from the locale, figure a way to temporarily, add the new entity and en-US string so at least the build will be usable.
- run the l10n builds through unittest or something similar before making available.
- use the same update generation logic as used for l10n releases.
...but anyone got other suggestions?
Reporter | ||
Updated•16 years ago
|
Summary: Produce updates for l10n nightly → Produce updates for l10n nightly builds
Updated•16 years ago
|
Component: Release Engineering → Release Engineering: Future
Priority: -- → P3
Updated•16 years ago
|
Whiteboard: [l10n]
Hello,
I would suggest adding this functionality to the standard en-US builds. As far as I understand, the l10n builds are derived from the en-US builds. If we had this code already there, we would not have to add it again and again every time we derive a l10n biuld from an en-US build.
Kind regards.
Comment 2•15 years ago
|
||
Hi Gerd, the localized builds do have the same update functionality as the en-US ones, and we use that for the release builds already. And we have en-US nightly updates, so mostly the work here is in infrastructure to produce the localised update files and offer them to users of nightly builds.
Reporter | ||
Updated•15 years ago
|
Assignee | ||
Comment 3•15 years ago
|
||
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
Assignee | ||
Updated•15 years ago
|
Assignee: nobody → ccooper
Status: NEW → ASSIGNED
Priority: P3 → P2
Assignee | ||
Comment 4•15 years ago
|
||
Currently available for mozilla-central and 1.9.2. We've decided against offering nightly updates to l10n users on the 1.9.1 branch (bug 511510) in favor of targeting a newer branch, e.g. lorentz.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•