[GODRIVER-1913] Clarify behavior for runOn.minServerVersion for latest servers Created: 08/Mar/21 Updated: 23/Mar/21 Resolved: 23/Mar/21 |
|
| Status: | Closed |
| Project: | Go Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Benji Rewis (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Documentation Changes: | Not Needed | ||||
| Description |
|
DRIVERS Ticket Description
Script Target - If you can read this text, the script has failed
|
| Comments |
| Comment by Benji Rewis (Inactive) [ 23/Mar/21 ] |
|
The Go driver unified test runner already follows the correct behavior. In particular, prerelease versions are treated as equivalent to actual releases when comparing server versions for both minServerVersion and maxServerVersion. |