This includes both the product repository version files, and the mozilla2/config.py and talos-pool/config.py files in buildbot-configs
...and the mozilla-central nagios monitoring files.
Created attachment 393175 [details] [diff] [review] bump mozilla-central to 1.9.3a1pre/3.7a1pre This should be landed on mozilla-central right after we branch. Note that I've updated all of the Nagios files for the branches tracking mozilla-central, too. This will cause a few false alarms until they all sync up - but it's easier to do them all at the same time.
Attachment #393175 - Flags: review?(catlee)
Attachment #393175 - Flags: review?(catlee) → review+
Re-assigning to bhearsum based on patch ownership.
Assignee: nobody → bhearsum
Priority: -- → P3
...do we need to refresh this after the version bump patches I landed during FF3.6a1 release last week?
(In reply to comment #4) > ...do we need to refresh this after the version bump patches I landed during > FF3.6a1 release last week? The removal parts of the patch are wrong, of course, but the rest of it is fine. It just means I have to apply it manually when I check in. I'm not going to bother posting and getting review on a new patch.
Comment on attachment 393175 [details] [diff] [review] bump mozilla-central to 1.9.3a1pre/3.7a1pre Checking in Firefox_electrolysis.txt; /cvsroot/mozilla/tools/tinderbox-configs/monitoring/Firefox_electrolysis.txt,v <-- Firefox_electrolysis.txt new revision: 1.3; previous revision: 1.2 done RCS file: /cvsroot/mozilla/tools/tinderbox-configs/monitoring/Firefox_mozilla-1.9.2.txt,v done Checking in Firefox_mozilla-1.9.2.txt; /cvsroot/mozilla/tools/tinderbox-configs/monitoring/Firefox_mozilla-1.9.2.txt,v <-- Firefox_mozilla-1.9.2.txt initial revision: 1.1 done Checking in Firefox_mozilla-central.txt; /cvsroot/mozilla/tools/tinderbox-configs/monitoring/Firefox_mozilla-central.txt,v <-- Firefox_mozilla-central.txt new revision: 1.14; previous revision: 1.13 done Checking in Firefox_places.txt; /cvsroot/mozilla/tools/tinderbox-configs/monitoring/Firefox_places.txt,v <-- Firefox_places.txt new revision: 1.3; previous revision: 1.2 done Checking in Firefox_tracemonkey.txt; /cvsroot/mozilla/tools/tinderbox-configs/monitoring/Firefox_tracemonkey.txt,v <-- Firefox_tracemonkey.txt new revision: 1.6; previous revision: 1.5 done RCS file: /cvsroot/mozilla/tools/tinderbox-configs/monitoring/XULRunner_mozilla-1.9.2.txt,v done Checking in XULRunner_mozilla-1.9.2.txt; /cvsroot/mozilla/tools/tinderbox-configs/monitoring/XULRunner_mozilla-1.9.2.txt,v <-- XULRunner_mozilla-1.9.2.txt initial revision: 1.1 done Checking in XULRunner_mozilla-central.txt; /cvsroot/mozilla/tools/tinderbox-configs/monitoring/XULRunner_mozilla-central.txt,v <-- XULRunner_mozilla-central.txt new revision: 1.3; previous revision: 1.2 done changeset: 31435:6fa9e4164629
Attachment #393175 - Flags: checked-in+
We're all done here.
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
(In reply to comment #6) > (From update of attachment 393175 [details] [diff] [review]) > Checking in Firefox_electrolysis.txt; > /cvsroot/mozilla/tools/tinderbox-configs/monitoring/Firefox_electrolysis.txt,v > <-- Firefox_electrolysis.txt > new revision: 1.3; previous revision: 1.2 > done Set the version back to 3.6a1pre as Electrolysis is merging from mozilla-central infrequently and is still using that version. We should probably just update Firefox_electrolysis.txt on an ad-hoc basis rather than with each release.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.