https://mongodb.slack.com/archives/GPZ8BPS3E/p1670615702122179

Atlas always uses the latest rapid release version on a branch. So, when a new rapid release version comes out, Atlas specific features no longer need to be tested on the old version. An example of this is serverless tests.

Essentially we only want to run Atlas specific tasks (serverless) in evergreen for rapid releases and need a way to specify tasks that only run for rapid releases.

We could manually stop running tasks on certain branches, but that is manual. Instead we can leverage mongo-task-generator.

We could start passing in a new var (ie: rapid_release_only) to the "generate resmoke tasks" function & then add the appropriate logic to mongo-task-generator to gen_tasks_activate.sh for determining whether the current mongo version is a rapid release or not. Based on that, we can either activate the task or not.