-
Type: Task
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
Server Tooling & Methods
If someone wants to patch-test a change, for example: when testing a 4.2 binary on 4.4, there's no easy way to make sure that the change works effectively on 4.4 and 4.2.
One way of addressing this might be to use evergreen modules for multiversion testing, so that patch-set-module could be used, if modules of the same repo are supported.