While doing Firefox 3.5.3 I realized that it was possible for both production-master and production-master02 to be polling the 3.5.3 candidates dir at the same time. If they were, they both would've kicked off l10nverify, updates, and verify steps, which would've been bad. Luckily, I only reconfig'ed one instance for this release so the other was still polling 3.6a1-candidates. We need to ensure this doesn't happen in the future. Possibly through one of these means: * Always using different release-* configs for each master * Turning off polling except when it's needed
Not going to get to this for awhile
Assignee: bhearsum → nobody
Component: Release Engineering → Release Engineering: Future
Now that we point different masters to different release configs this isn't such an issue.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WORKSFORME
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.