[CDRIVER-3858] Continuous Matrix Testing Created: 14/Jan/21  Updated: 06/May/22

Status: Backlog
Project: C Driver
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Epic Priority: Major - P3
Reporter: Alexander Golin (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
Quarter: FY22Q1

 Description   
Epic Summary

Motivation

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.

Note we also want to include Atlas dedicated and shared tier instances in this testing matrix.

Cast of Characters

Lead: Jeff Yemin
Author: Eric Adum
POCs: C/CXX (Kevin)
Program Manager: Alexander Golin
Product Owner: Rachelle Palmer

Documentation

Scope
Design


Generated at Wed Feb 07 21:19:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.