• Branch system_perf.yml for 4.8
  • Change most references from "master" to "v4.8" Remove the wt-develop variants from the v4.8 commit

• Branch evergreen.yml for 4.8
  • After branching, in the 4.8 branch:
    • Change most references from "master" to "v4.8"
    • Remove the wt-develop variants from the v4.8 commit See work done in SERVER-35158.

• Remove wt develop from system-perf.yml and evergreen.yml
  • Similar to what we've done for previous releases, the wt-develop build variants should be removed from the release MongoDB branches.

• Update filename suffix to v4.8-latest for nightly builds for 4.8 branch
  • After branching 4.8, we should follow the same steps we when we branch 4.0 in SERVER-35162.

• Update multiversion tests following 4.8 branch
  • See SERVER-31553 for the work done when branching 3.6. This should be done with as part of the upgrade/downgrade project Similar to SERVER-27107, after branching 4.8, we should bump the version in the following places:
  • For master branch:
    • update multiversion to download 4.8: https://github.com/mongodb/mongo/blob/r4.8-rc0/etc/evergreen.yml#L975
    • update MongoRunner.binVersionSubs
    • bump verify_versions_test.js from 4.8 to 4.9.0Dev
    • remove any multiversion tests that are specifically testing 4.4 <~~> 3.new upgrade/downgrade scenarios.

• (4.8) Update perf.yml to use 4.8 enterprise module
  • https://github.com/mongodb/mongo/blob/e291cbea1741b9536340bd67c1311b9fff3381bd/etc/perf.yml#L50 https://github.com/mongodb/mongo/blob/dbb9a7c7acd0c3e97ff128c4eaa225b6567d2249/etc/system_perf.yml#L766

All of these main bullet points should be a separate commit but they should be pushed together in the same commit queue task. The reason they should be pushed as separate commits is in the case of needing to revert one aspect of this entire task.