While these machines could be restored from tape backup if needed, doing that is non-trivial, so should only be considered as last resort.
What will change:
- no longer produce FF2.0.0.x incremental/depend/hourly builds
- no longer produce FF2.0.0.x clobber/nightly builds
- no longer produce FF2.0.0.x release builds
- remove the FF2.0.0.x waterfall page on tinderbox, as it will be empty.
What will *not* change:
- FF126.96.36.199 builds would still be available for download from http://www.mozilla.com/en-US/firefox/all-older.html.
- existing update offers would still be available. For example:
- FF188.8.131.52 users who do check for update will still get updated to FF184.108.40.206.
- FF220.127.116.11 users who do check for update will still get updated to FF3.0.5.
- newly revised major update offers, like from FF18.104.22.168 -> FF3.0.9, could still be produced as needed (because these are produced on the FF3.0.x infrastructure, not on the powered off FF2 infrastructure.)
- Thunderbird2.0.0.x use 9 other machines for doing builds, etc. These are not being touched, and will continue to be supported as usual until EOL after Thunderbird 3.0 ships.
Why do this:
- reuses some of these machines in production pool-of-slaves or try pool-of-slaves, where there is more demand
- reduce manual support workload 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 FF2 specific situations.
What machines are we talking about: