Uploaded image for project: 'Rust Driver'
  1. Rust Driver
  2. RUST-1735

Implement Rust driver 3.0

XMLWordPrintableJSON

    • Type: Icon: Epic Epic
    • Resolution: Fixed
    • Priority: Icon: Unknown Unknown
    • 3.0.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Done
    • Rust Driver 3.0
    • Hide

      Engineers: Abraham + Isabel

      2024-04-12: Updated target date to 2024-04-19

      What was accomplished since the last update?

      • Driver changes completed.

      What goals are we targeting for the next two weeks?

      • Write migration guide.

      Are there any risks to the current project timeline?

      • Waiting to release near server 8.0 release date.

      2024-03-28: Target date updated to April 12 (+2wks)

      • Target date updated, as some work jumped priority (addressing a endianness bug + urgent test fixes).
      • What was accomplished since the last update?
        • Improved handling around options depending on feature flags.
        • GridFS fluent API merged.
        • Search Index fluent API merged.
      • What goals are we targeting for the next two weeks?
        • Make remaining fluent API changes.
      • Do we need to consider re-evaluating the scope of the project?
        • I think "no". Remaining work appears small enough to avoid extended delays.

      2024-03-14:

      • What was accomplished since the last update?
        • Fluent API changes put into review.
        • Removed deprecated server_id field.
      • What goals are we targeting for the next two weeks?
        • Improve handling around options depending on feature flags.

      2024-03-01:

      • What was completed over the last two weeks?
        • Support for async-std removed.
        • Fluent API changes in progress.
      • What's the focus over the next two weeks?
        • Improved handling around options depending on feature flags.

      2024-02-16: 

      No notable updates. Work temporarily paused to focus on "Common Drivers FaaS Improvements" prioritized for the start of Q1.

      2024-02-02: Updated target end date to 03-15-2024

      Status update:

      • Revisit async runtime support in progress.
      • Reducing helper boilerplate is in review.

      2024-01-19: No change to End-Date

      Status update:

      • Reducing helper boilerplate is in review.
      • Internal document approved for revised APM API. Implementation in progress.

      2024-01-05: No change to End-Date.

      Status update:

      • Reducing helper boilerplate is in review.
      • Internal document approved for revised APM API. Implementation in progress.

      2023-12-20: No change to End-Date.

      Status update:

      • Internal document approved for revised APM API. Implementation in progress.
      • Internal document for fluent options approved.

      2023-12-11: Setting initial End-Date to 2023-03-01

      Status update:

      • Scope approved.
      • Internal document in review for revised APM API.
      • Revisiting shutdown behavior scheduled.
      Show
      Engineers: Abraham + Isabel 2024-04-12: Updated target date to 2024-04-19 What was accomplished since the last update? Driver changes completed. What goals are we targeting for the next two weeks? Write migration guide. Are there any risks to the current project timeline? Waiting to release near server 8.0 release date. 2024-03-28: Target date updated to April 12 (+2wks) Target date updated, as some work jumped priority (addressing a endianness bug + urgent test fixes). What was accomplished since the last update? Improved handling around options depending on feature flags. GridFS fluent API merged. Search Index fluent API merged. What goals are we targeting for the next two weeks? Make remaining fluent API changes. Do we need to consider re-evaluating the scope of the project? I think "no". Remaining work appears small enough to avoid extended delays. 2024-03-14: What was accomplished since the last update? Fluent API changes put into review. Removed deprecated server_id field. What goals are we targeting for the next two weeks? Improve handling around options depending on feature flags. 2024-03-01: What was completed over the last two weeks? Support for async-std removed. Fluent API changes in progress. What's the focus over the next two weeks? Improved handling around options depending on feature flags. 2024-02-16:  No notable updates. Work temporarily paused to focus on "Common Drivers FaaS Improvements" prioritized for the start of Q1. 2024-02-02: Updated target end date to 03-15-2024 Status update: Revisit async runtime support in progress. Reducing helper boilerplate is in review. 2024-01-19: No change to End-Date Status update: Reducing helper boilerplate is in review. Internal document approved for revised APM API. Implementation in progress. 2024-01-05: No change to End-Date. Status update: Reducing helper boilerplate is in review. Internal document approved for revised APM API. Implementation in progress. 2023-12-20: No change to End-Date. Status update: Internal document approved for revised APM API. Implementation in progress. Internal document for fluent options approved. 2023-12-11: Setting initial End-Date to 2023-03-01 Status update: Scope approved. Internal document in review for revised APM API. Revisiting shutdown behavior scheduled.
    • 20.5
    • 17
    • 20.5
    • 100

      Summary

      Release a new major version of the Rust driver with backwards-incompatible changes.

      Motivation

      Who is the affected end user?

      Users of the driver.

      How does this affect the end user?

      Current driver shortcomings are not hard blockers but often require awkward workarounds.

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

      The issues impact almost every use of the driver.

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

      Mild to moderate - frustration and ongoing engineering needed for workarounds.

      Is this issue urgent?

      No

      Is this ticket required by a downstream team?

      No

      Is this ticket only for tests?

      No

      Cast of Characters

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

      Channels & Docs

      Slack Channel

      Scope Document

      [Technical Design Document|some.url]

            Assignee:
            abraham.egnor@mongodb.com Abraham Egnor
            Reporter:
            abraham.egnor@mongodb.com Abraham Egnor
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              18 weeks, 1 day