Closed Bug 464170 Opened 16 years ago Closed 16 years ago

do l10n releases in Firefox3.0 by using the same logic as it gets used for nightly builds

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: armenzg, Unassigned)

References

Details

We currently do Firefox3.0 releases by doing l10n repackages using Bootstrap and tinderbox. Let's do the releases by adding the logic that is being used for nightly builds - each locale is an independent build object that any slave can take (parallelization)
Blocks: 464171
Depends on: 451225
With all of the other l10n work we have going, why is this a priority? I don't see _any_ benefit from switching to the new system. We only have one slave setup for releases, we're not even going to benefit from parallelizing. I am extremely hesitant to change our release system without clear benefit. And I'm especially hesitant to do it while we have other places where we have _no_ l10n system at all.
Summary: do releases in Firefox3.0 by using the same logic as it gets used for nightly builds → do l10n releases in Firefox3.0 by using the same logic as it gets used for nightly builds
I agree with Ben here 100%. We have a working system for 3.0, so let's not change it. Let's tackle 3.1 and onward with the new system.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.