[DRIVERS-1608] Spec: Continuous Matrix Testing Created: 28/May/20 Updated: 06/May/22 Resolved: 04/Dec/20 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | Spec Change | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | DRIVERS-721 |
| Quarter: | FY22Q1 |
| Description |
|
Epic Summary MotivationWe often get questions from the internal driver users (e.g. the cloud and enterprise tools teams, mlab), the field team and customers along the lines of "we're upgrading to MongoDB version X.Y.Z, will the driver we currently use, which shipped years ago with MongoDB version A.B.C continue to work?". We've mostly been able to answer that question by assuring users that they can upgrade to the latest driver version first, since that driver supports MongoDB versions all the way back to 2.6. Atlas upgrade schedules, mlab migrations to Atlas and an increasing rate of backward breaking changes in the server have complicated the situation. This project tracks testing a matrix of driver and server versions. For example, the last patch release of the driver version that first shipped support for MongoDB 3.6 would be tested, triggered by server branch commits, against the head of MongoDB 4.0, 4.2, 4.4, etc. Note we also want to include Atlas dedicated and shared tier instances in this testing matrix. Cast of CharactersLead: Jeff Yemin DocumentationScope See DRIVERS-721 for updated details. |
| Comments |
| Comment by Alexander Golin (Inactive) [ 04/Dec/20 ] |
|
No changes to the spec repo for this project. |