We have a few Evergreen builders (listed below) expected to be executed only on the "WiredTiger (develop)" Evergreen project. Those builders should be disabled on other WiredTiger Evergreen projects that are set up to test against non-develop (or release) branches. 

• ubuntu2004-perf-tests
• documentation-update
• code-statistics
• compatibility-tests-less-frequent
• compatibility-tests-daily
• compatibility-tests

In the past, we used the "activate: false" Evergreen argument setting (needs Evergreen yaml code change) to disable these builders on Evergreen projects (WT-9255 as an example) that correspond to a newer release branch once it's branched out from the main/develop branch. We should explore ways to achieve the builder disabling target without ongoing maintenance effort. Please note we need to branch out every quarter at the moment (following the rapid release cycle) and might increase the frequency further in the future.