Node V7

XMLWordPrintableJSON

    • Type: Epic
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Node V7
    • Node Drivers
    • None
    • Hide
      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?
      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • In Progress
    • 10
    • 17.5
    • 18
    • 100
    • 80
    • 🟢 On Track
    • Hide

      Engineer(s): Bailey Pearson, Durran Jordan, Sergey Zelenov, Pavel Safronov

      What was accomplished since the last update?

      • Completed all planned changes for V7 and drafted all release notes
      • Alpha releases for all libraries handed off to dev tools and mongoose for testing
      • Finished all callback test migrations

      What's the focus over the next two weeks?

      • Officially deprecate `mongodb-legacy`
      • Address any issues uncovered by dev tools and mongoose testing (if any)
      • Officially release major versions of all libraries (planned week of Nov 3)

      Any risks/blockers/impediments?

      • None anticipated from this point
      Show
      Engineer(s): Bailey Pearson, Durran Jordan, Sergey Zelenov, Pavel Safronov What was accomplished since the last update? Completed all planned changes for V7 and drafted all release notes Alpha releases for all libraries handed off to dev tools and mongoose for testing Finished all callback test migrations What's the focus over the next two weeks? Officially deprecate `mongodb-legacy` Address any issues uncovered by dev tools and mongoose testing (if any) Officially release major versions of all libraries (planned week of Nov 3) Any risks/blockers/impediments? None anticipated from this point
    • Hide

      2025-10-24 - 🟢 On Track
      Engineer(s): Bailey Pearson, Durran Jordan, Sergey Zelenov, Pavel Safronov

      What was accomplished since the last update?

      • Completed all planned changes for V7 and drafted all release notes
      • Alpha releases for all libraries handed off to dev tools and mongoose for testing
      • Finished all callback test migrations

      What's the focus over the next two weeks?

      • Officially deprecate `mongodb-legacy`
      • Address any issues uncovered by dev tools and mongoose testing (if any)
      • Officially release major versions of all libraries (planned week of Nov 3)

      Any risks/blockers/impediments?

      • None anticipated from this point

      2025-10-10 - 🟢 On Track
      Engineer(s): Bailey Pearson, Durran Jordan, Sergey Zelenov, Pavel Safronov

      What was accomplished since the last update?

      • Completed AWS credentials in the URI spec work (node implementation in review)
      • Completed work to remove driver deprecations
      • Completed mongodb-client-encryption breaking changes (and released an alpha), along with all expected changes to native packages
      • Majority of legacy callback test migrations complete

      What's the focus over the next two weeks?

      • Wrap up breaking changes in the driver and bson libraries
      • Complete the callback test migrations
      • Release alphas of all libraries and get shell and mongoose to test the changes before we move forward with an official release

      Any risks/blockers/impediments?

      • We ran into some additional glibc issues when we went to release the FLE bindings alpha and discovered and fixed a minor bug in the course of working on one of the V7 driver tickets, which may ultimately result in a slight bump to the final cost estimate; but we still anticipate being code-complete by the target calendar date

      2025-09-26 - 🟢 On Track
      Engineer(s): Bailey Pearson, Durran Jordan, Sergey Zelenov, Pavel Safronov

      Note: We are adding 5 eng weeks to the final cost estimate to account for the pace of the two new hires working on this project as well as the unexpected bumps we encountered during our platform updates (e.g., Python version issues with node-gyp, a minor bug in the Node.js runtime).

      What was accomplished since the last update?

      • Completed AWS custom credential provider spec work in review (DRIVERS-3207) along with the Node implementation
      • Completed work to remove support for Node versions 16 and 18 from all libraries and associated platform updates
      • Completed work to remove callback support from kerberos
      • Started the legacy callback test migration to async/await (in order to deprecate the legacy driver)

      What's the focus over the next two weeks?

      • Complete AWS spec and driver work concerning URI options (DRIVERS-3131)
      • Complete the legacy callback test migration to async/await
      • Continue working down the V7 ticket list in priority order: next up is mongodb-client-encryption changes

      Any risks/blockers/impediments?

      • None anticipated now that the platform updates are complete

      2025-09-16 - 🟢 On Track
      Engineer(s): Bailey Pearson, Durran Jordan

      Completed over the last 2 weeks:

      • Just started work on the project
      • Associated AWS credential spec work in review (DRIVERS-3207) along with the Node implementation
      • Started removing support for Node versions 16 and 18 from add-on libraries
      • Started work to remove callback support from kerberos

      Focus over the next 2 weeks:

      • Continue working down the V7 ticket list in priority order: next up is the work to remove callbacks from our test suite that will allow us to drop support for the legacy driver.

      2025-09-12 - No confidence status provided
      No project update provided

      Show
      2025-10-24 - 🟢 On Track Engineer(s): Bailey Pearson, Durran Jordan, Sergey Zelenov, Pavel Safronov What was accomplished since the last update? Completed all planned changes for V7 and drafted all release notes Alpha releases for all libraries handed off to dev tools and mongoose for testing Finished all callback test migrations What's the focus over the next two weeks? Officially deprecate `mongodb-legacy` Address any issues uncovered by dev tools and mongoose testing (if any) Officially release major versions of all libraries (planned week of Nov 3) Any risks/blockers/impediments? None anticipated from this point 2025-10-10 - 🟢 On Track Engineer(s): Bailey Pearson, Durran Jordan, Sergey Zelenov, Pavel Safronov What was accomplished since the last update? Completed AWS credentials in the URI spec work (node implementation in review) Completed work to remove driver deprecations Completed mongodb-client-encryption breaking changes (and released an alpha), along with all expected changes to native packages Majority of legacy callback test migrations complete What's the focus over the next two weeks? Wrap up breaking changes in the driver and bson libraries Complete the callback test migrations Release alphas of all libraries and get shell and mongoose to test the changes before we move forward with an official release Any risks/blockers/impediments? We ran into some additional glibc issues when we went to release the FLE bindings alpha and discovered and fixed a minor bug in the course of working on one of the V7 driver tickets, which may ultimately result in a slight bump to the final cost estimate; but we still anticipate being code-complete by the target calendar date 2025-09-26 - 🟢 On Track Engineer(s): Bailey Pearson, Durran Jordan, Sergey Zelenov, Pavel Safronov Note: We are adding 5 eng weeks to the final cost estimate to account for the pace of the two new hires working on this project as well as the unexpected bumps we encountered during our platform updates (e.g., Python version issues with node-gyp, a minor bug in the Node.js runtime). What was accomplished since the last update? Completed AWS custom credential provider spec work in review ( DRIVERS-3207 ) along with the Node implementation Completed work to remove support for Node versions 16 and 18 from all libraries and associated platform updates Completed work to remove callback support from kerberos Started the legacy callback test migration to async/await (in order to deprecate the legacy driver) What's the focus over the next two weeks? Complete AWS spec and driver work concerning URI options ( DRIVERS-3131 ) Complete the legacy callback test migration to async/await Continue working down the V7 ticket list in priority order: next up is mongodb-client-encryption changes Any risks/blockers/impediments? None anticipated now that the platform updates are complete 2025-09-16 - 🟢 On Track Engineer(s): Bailey Pearson, Durran Jordan Completed over the last 2 weeks: Just started work on the project Associated AWS credential spec work in review ( DRIVERS-3207 ) along with the Node implementation Started removing support for Node versions 16 and 18 from add-on libraries Started work to remove callback support from kerberos Focus over the next 2 weeks: Continue working down the V7 ticket list in priority order: next up is the work to remove callbacks from our test suite that will allow us to drop support for the legacy driver. 2025-09-12 - No confidence status provided No project update provided
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Summary

      What is the problem or use case, what are we trying to achieve?

      Motivation

      Who is the affected end user?

      Who are the stakeholders?

      How does this affect the end user?

      Are they blocked? Are they annoyed? Are they confused?

      How likely is it that this problem or use case will occur?

      Main path? Edge case?

      If the problem does occur, what are the consequences and how severe are they?

      Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete?

      Is this issue urgent?

      Does this ticket have a required timeline? What is it?

      Is this ticket required by a downstream team?

      Needed by e.g. Atlas, Shell, Compass?

      Is this ticket only for tests?

      Is this ticket have any functional impact, or is it just test improvements?

      Cast of Characters

      Engineering Lead:
      Document Author:
      POCers:
      Product Owner:
      Program Manager:
      Stakeholders:

      Channels & Docs

      Slack Channel

      [Scope Document|some.url]

      [Technical Design Document|some.url]

            Assignee:
            Daria Pardue
            Reporter:
            Daria Pardue
            Daria Pardue Daria Pardue
            None
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              7 weeks
              None
              None
              None