Uploaded image for project: 'Go Driver'
  1. Go Driver
  2. GODRIVER-1835

Continuous Matrix Testing

    • Type: Icon: Epic Epic
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Hide

      Engineer(s): Divjot

      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 | 1 To Date | 1 Est Final

      2021-03-09: Initial target end date of 2021-03-05

      • The main PRs have all been merged, but there's one last Go-specific ticket that Divjot filed for the project. It'll require Kevin's review (he is OOO this week and next) and Divjot is not planning on starting it until Kevin returns
      • On pause for the next 2 weeks. Target end date will be updated once this is picked back up

      Show
      Engineer(s): Divjot 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 | 1 To Date | 1 Est Final 2021-03-09: Initial target end date of 2021-03-05 The main PRs have all been merged, but there's one last Go-specific ticket that Divjot filed for the project. It'll require Kevin's review (he is OOO this week and next) and Divjot is not planning on starting it until Kevin returns On pause for the next 2 weeks. Target end date will be updated once this is picked back up

      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

            Assignee:
            divjot.arora@mongodb.com Divjot Arora (Inactive)
            Reporter:
            backlog-server-pm Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:
              4 days