Use Case

As a... (who is this for)
I want... (what is the desired change)
So that... (why is the change desired)

User Experience

• What is the desired/expected outcome for the user once this ticket is implemented?
• If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?

Dependencies

• upstream and/or downstream requirements and timelines to bear in mind

Risks/Unknowns

• Is the intention to only stop relying on mongodb-legacy for testing?
  • No - we'd like to both stop testing with mongodb-legacy and to stop releasing major versions of mongodb-legacy for each new driver major.
• What is the motivation for dropping support?
  • mongodb-legacy was never intended to be a long-term maintained product - it was intended as a driver alternative.
• Are users using our latest features with callback support via mongodb-legacy?
  • Unsure.
• What is the relation of this work to driver v7? Is v7 going to contain a change that will break the legacy package?
  • mongodb-legacy is compatible with the same major version of the driver.  If we decide to stop supporting mongodb-legacy, the change must be made in a major version.  This ticket is a placeholder to track the potential removal of support for mongodb-legacy.

Acceptance Criteria

Implementation Requirements

• functional reqs, potential snafus to avoid, performance targets, etc

Testing Requirements

• unit test, spec test sync, etc

Documentation Requirements

• DOCSP ticket, API docs, etc

Follow Up Requirements

• additional tickets to file, required releases, etc
• if node behavior differs/will differ from other drivers, confirm with dbx devs what standard to aim for and what plan, if any, exists to reconcile the diverging behavior moving forward