Implement Rust BSON library 3.0

XMLWordPrintableJSON

    • Type: Epic
    • Resolution: Unresolved
    • Priority: Unknown
    • bson-3.0.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Rust BSON 3.0
    • Rust 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?
    • To Do
    • None
    • 18
    • 4
    • 16
    • 100
    • -11
    • None
    • Hide

      2025-06-18: Setting end-date to 2025-07-25

      Who actively worked on the project in the last two weeks?

      • Abraham and Isabel

      What was accomplished since the last update?

      • Prep work in driver for upcoming major BSON release complete.
      • UTF-8 performance improvement merged (changes error type).

      What goals are we targeting for the next two weeks?

      • Decouple en/decoding from [de]serialization (avoids parsing ambiguity)
      • Consolidate error types
      Show
      2025-06-18: Setting end-date to 2025-07-25 Who actively worked on the project in the last two weeks? Abraham and Isabel What was accomplished since the last update? Prep work in driver for upcoming major BSON release complete. UTF-8 performance improvement merged (changes error type). What goals are we targeting for the next two weeks? Decouple en/decoding from [de] serialization (avoids parsing ambiguity ) Consolidate error types

      Summary

      Release a new version of the Rust BSON library ("crate") with backwards-incompatible changes.

      Motivation

      Who is the affected end user?

      Users of the drivers.

      How does this affect the end user?

      Current library shortcomings are not blockers but either require awkward workarounds or incur substantial resource usage penalties.

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

      It would be difficult to use the current BSON library and not run into these issues.

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

      Extra resource usage and engineer frustration.

      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

      Scope Document

            Assignee:
            Abraham Egnor
            Reporter:
            Abraham Egnor
            None
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              6 weeks, 4 days
              None
              None
              None