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 All tickets in code review Adding two weeks to address comments and wrap up, but the epic would likely close before 4/2 2021-03-09: Updating target end date to 2021-03-19 Kinda blocked by PM-1607. Mikalai is currently trying to work around this issue. If successful, this will wrap up by the end of this week. If not, it will be done after the EVG epic is complete which will be by the end of this month 2021-02-23: Updating target end date to 2021-03-05 Testing on 4.0, 4.2, and 4.4 in progress. Ran into some build issues last week which slowed things down Mikalai is OOO this week 2021-02-09: Setting initial target end date to 2021-02-19 Currently working on testing MongoDB 4.0-era Driver Support Mikalai ran into some build issues which caused some delays and have been resolved He is the first responder for user tickets this week Testing for 4.2 will be up next