Issue Summary

John Daniels asked whether the WiredTiger test configuration for MongoDB 7.0 should be updated to stop using macOS 11 and instead run on macOS 14. He noted that the mongodb-7.0 branch of WiredTiger already compiles successfully on macOS 14 and that the change appears trivial in the main MongoDB code base.

Context

• The thread is in #ask-wiredtiger and references a successful Evergreen run on macOS 14: spruce.corp.mongodb.com/version/6aad5cccd911e60007ef220d
• A response from tiger-bot indicated that for MongoDB 7.0, the existing macOS 11 testing should be left in place for now.
• The guidance provided was that migrating 7.0 to macOS 14 would be a substantial CI/test-policy change without a compelling product reason, even though macOS 14 is now the oldest supported macOS.
• If pursued, the recommended process is to:
  • File a WT ticket describing the macOS 11 -> 14 CI migration and link the successful Evergreen run.
  • Open the corresponding PR in the WiredTiger test configuration; `test/evergreen.yml` already contains macOS 14-specific configuration and build variants.
  • Include the Evergreen patch link and follow the WiredTiger contribution guidance in AGENTS.md, including validation via `dist/s_all` or `dist/s_fast`.
  • Coordinate with Storage Engines/Persistence before changing the 7.0 branch.

Proposed Solution

• Create a WT ticket and associated PR for the macOS 11 -> macOS 14 migration in WiredTiger CI.
• Attach the successful Evergreen run as evidence that the branch builds on macOS 14.
• Do not merge the change unilaterally; obtain Storage Engines/Persistence approval because this is a maintenance/test policy decision rather than a build fix.

Original Slack thread: https://mongodb.slack.com/archives/C2YEQ607N/p1789749803748899
This ticket was generated by AI from a Slack thread.