[CSHARP-3328] Continuous Matrix Testing Created: 14/Jan/21 Updated: 06/May/22 Resolved: 29/Mar/21 |
|
| Status: | Closed |
| Project: | C# Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Epic | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Mikalai Mazurenka (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Quarter: | FY22Q1 | ||||
| Start date: | |||||
| End date: | |||||
| Calendar Time: | 8 weeks, 3 days | ||||
| Detailed Project Statuses: | Engineer(s): Mikalai Summary: We 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. Cost in Eng Weeks: 2 Original | 4 To Date | 6 Est Final 2021-03-23: Updating target end date to 2020-04-02
2021-03-09: Updating target end date to 2021-03-19
2021-02-23: Updating target end date to 2021-03-05
2021-02-09: Setting initial target end date to 2021-02-19
|
||||
| Description |