We have a subdirectory of multiversion tests called targetedTestsLastLtsFeatures, which holds tests that verify behavior between lastLTS and latest. These tests should be removed for each major release, since lastLTS only changes in each major release. For rapid releases, these tests should not be removed.

It seems in SERVER-65140, we stopped running tests in targetedTestsLastLtsFeatures in the future git tag variant since we expected the tests to be removed after the next release. I believe this is correct only if our next release is a major release. If it is a rapid release, we are losing test coverage in verifying that targeted last LTS tests work as expected regardless of which rapid release we are on.

I think we should re-enable those tests in the future git tag variant and consider disabling them whenever the next release is a major release. But I don’t think it’s a significant improvement to avoid running those tests just for the few months where we are ramping up to a major release.