Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-3001

MongoDB Stable API for Drivers

    • Type: Icon: Epic Epic
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 4.0.0
    • Affects Version/s: None
    • Component/s: None
    • Not Needed
    • Done
    • Versioned API
    • Hide

      Engineer(s): Eric Adum
      Summary: This epic is used to track Node's implementation of Versioned API

      Cost in Eng Weeks: 2 Original | 10 To Date | 12 Est Final
      2020-06-30: Updating target date to 2021-07-09

      • The team has backported Versioned API and hello to 3.7 and has addressed a small error bug in 3.7 as well.
      • Currently in progress is updating the 3.7 serverApi implementation to validate version, sized as a very small effort.
      • Otherwise there are two very small tickets at the top of our scheduled queue to update a server parameter name and provide usage examples to docs.

      Cost in Eng Weeks: 2 Original | 8 To Date | 10 Est Final
      2020-06-16: Updating target date to 2021-06-25

      • Node is now backporting VersionedAPI to 3.7
      • There are some small follow up tasks to complete for 4.0, but the core functionality is complete.

      2020-04-06: Updating target date to 2021-04-23

      • The core implementation of versioned API is complete and the final follow up tasks (e.g. documentation and code samples) are in review.
      • The team identified that they will need to backport this work to the 3.x version of the driver, so we have filed an additional ticket in this epic for this effort. This will take some additional time so bumping out the target date past skunkworks.

      Cost in Eng Weeks: 2 Original | 6 To Date | 7 Est Final

      2020-03-23: Updating target date to 2021-04-02

      • The core implementation of versioned API is complete, this epic is just pending several small follow up tasks.
      • Eric has had to split his attention between this and user issues.
      • Extending end date by 2 weeks due to generally high user issue influx.

      Cost in Eng Weeks: 2 Original | 5 To Date | 6 Est Final

      2020-03-09: Updating target date to 2021-03-19

      • This project is now in code review!
      • There are some very small clean up and documentation tickets remaining, aiming to wrap this week.
      • Extending the end date by one week to allow time for code review.

      Cost in Eng Weeks: 2 Original | 4 To Date | 5 Est Final

      2020-02-23: Updating target date to 2021-03-12

      • Eric has been continuing to make progress on implementation though has had to spend some amount of his time investigating user issues.
      • Extending the date 2 weeks past BuildFest - while there is likely not 2 weeks of work left, I think it would be prudent to allot some extra time for review and feedback.

      Cost in Eng Weeks: 2 Original | 2 To Date | 3 Est Final

      2020-02-09: Setting target date to 2021-02-19

      • Neal's progress on Unified Test Format has unblocked Eric to begin working on Versioned API.
      • Steadily progressing now that the work is unblocked. While the core implementation may complete this week, adding another week to account for review time and some slight follow up documentation effort.
      Show
      Engineer(s): Eric Adum Summary: This epic is used to track Node's implementation of Versioned API Cost in Eng Weeks: 2 Original | 10 To Date | 12 Est Final 2020-06-30: Updating target date to 2021-07-09 The team has backported Versioned API and hello to 3.7 and has addressed a small error bug in 3.7 as well. Currently in progress is updating the 3.7 serverApi implementation to validate version, sized as a very small effort. Otherwise there are two very small tickets at the top of our scheduled queue to update a server parameter name and provide usage examples to docs. Cost in Eng Weeks: 2 Original | 8 To Date | 10 Est Final 2020-06-16: Updating target date to 2021-06-25 Node is now backporting VersionedAPI to 3.7 There are some small follow up tasks to complete for 4.0, but the core functionality is complete. 2020-04-06: Updating target date to 2021-04-23 The core implementation of versioned API is complete and the final follow up tasks (e.g. documentation and code samples) are in review. The team identified that they will need to backport this work to the 3.x version of the driver, so we have filed an additional ticket in this epic for this effort. This will take some additional time so bumping out the target date past skunkworks. Cost in Eng Weeks: 2 Original | 6 To Date | 7 Est Final 2020-03-23: Updating target date to 2021-04-02 The core implementation of versioned API is complete, this epic is just pending several small follow up tasks. Eric has had to split his attention between this and user issues. Extending end date by 2 weeks due to generally high user issue influx. Cost in Eng Weeks: 2 Original | 5 To Date | 6 Est Final 2020-03-09: Updating target date to 2021-03-19 This project is now in code review! There are some very small clean up and documentation tickets remaining, aiming to wrap this week. Extending the end date by one week to allow time for code review. Cost in Eng Weeks: 2 Original | 4 To Date | 5 Est Final 2020-02-23: Updating target date to 2021-03-12 Eric has been continuing to make progress on implementation though has had to spend some amount of his time investigating user issues. Extending the date 2 weeks past BuildFest - while there is likely not 2 weeks of work left, I think it would be prudent to allot some extra time for review and feedback. Cost in Eng Weeks: 2 Original | 2 To Date | 3 Est Final 2020-02-09: Setting target date to 2021-02-19 Neal's progress on Unified Test Format has unblocked Eric to begin working on Versioned API. Steadily progressing now that the work is unblocked. While the core implementation may complete this week, adding another week to account for review time and some slight follow up documentation effort.

      Epic Summary

      Summary
      Introduce new options in all drivers to allow users to select an API version when connecting to a MongoDB instance.

      Motivation
      As MongoDB moves toward more frequent releases (a.k.a. continuous delivery), we want to enable users to take advantage of our rapidly released features, without exposing applications to incompatible server changes due to automatic server upgrades. A versioned API will help accomplish that goal.

      Cast of Characters

      Lead: Jeff Yemin
      Author: Andreas Braun
      POCs: Rust - Andreas, Ruby - Emily
      Product Owner:

      Documentation

      Scope Document
      Technical Design Document

            Assignee:
            eric.adum@mongodb.com Eric Adum (Inactive)
            Reporter:
            alexander.golin@mongodb.com Alexander Golin (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              22 weeks, 4 days