[SERVER-81253] Run targeted lastLTS tests in future git tag variant Created: 20/Sep/23 Updated: 29/Oct/23 Resolved: 05/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Xuerui Fa | Assignee: | Steve Gross |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Server Development Platform
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Participants: | |||||
| Description |
|
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
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. |
| Comments |
| Comment by Githook User [ 04/Oct/23 ] |
|
Author: {'name': 'Steve Gross', 'email': 'steve.gross@mongodb.com', 'username': 'stevegrossmongodb'}Message: |
| Comment by Tausif Rahman (Inactive) [ 29/Sep/23 ] |
|
That sounds right to me. |