Now that Firefox5.0 shipped, we’ve got time to go back and do some cleanup. We’re going to disable the Firefox3.5 jobs this week.
This was already announced in last week’s platform meeting , but after all those years, its quite possible that people are relying on those jobs in ways we do not even know about. Hence this widespread notice. If you have any reasons these Firefox 3.5 jobs should be left running, please let us know by commenting in bug#666407.
- What will change:
- No FF3.5.x incremental/depend/hourly builds will be produced.
- No FF3.5.x clobber/nightly builds will be produced.
- No FF3.5.x release builds will be produced.
- The FF3.5 waterfall page will be removed from tinderbox. Specifically, this page http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox3.5 will go away as it will be empty.
- What will *not* change:
- Existing FF3.5.x builds would still be available for download from http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/
- Existing update offers would still be available. For example:
- FF3.5.14 users can still update to FF3.5.19.
- FF3.5.19 users can still update to latest FF3.6.x release (which is FF3.6.18 as of this writing).
- Newly revised major update offers, like from FF3.5.19 -> a future FF3.6.19 release, could still be produced if needed
- Any mozilla-1.9.1 machines which are not Firefox specific should continue to run as usual.
- Why do this:
- Free up compute cycles in the shared production pool-of-slaves or try
pool-of-slaves. This will help make life better for all other jobs.
- Reduce manual support workload and systems complexity for RelEng and IT.
- Allows us speed up making changes to infrastructure code, as there’s now no longer a need to special-case and retest FF3.5 specific situations.
If you have any reasons that these Firefox3.5 jobs should continue running, please comment in bug#666407. Now.