Closed
Bug 609887
Opened 14 years ago
Closed 14 years ago
We should not need to move specific 10.6 slaves for l10n repacking releases
Categories
(Release Engineering :: General, defect, P4)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Unassigned)
References
Details
(Whiteboard: [releases])
When we do releases we should not need to move specific 10.6 slaves to do L10n repackages: http://production-master.build.mozilla.org:8010/builders/macosx64_repack For e.g. moz2-darwin10-slave[05-12] This won't be an issue once we move releases to schedulerDB.
Updated•14 years ago
|
Summary: We should not need to move specific 10.6 slave for releases → We should not need to move specific 10.6 slaves for l10n repacking releases
Reporter | ||
Updated•14 years ago
|
Priority: -- → P4
Whiteboard: [releases]
Reporter | ||
Comment 1•14 years ago
|
||
This got fixed when we merged the release and builders' pool.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Assignee | ||
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
•