[GODRIVER-2371] Determine the best way to support both v1.x and v2.x drivers Created: 07/Apr/22  Updated: 17/Apr/23  Resolved: 17/Apr/23

Status: Closed
Project: Go Driver
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Unknown
Reporter: Matt Dale Assignee: Matt Dale
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: Go Driver 2.0 Scope
Quarter: FY23Q4
Documentation Changes: Not Needed
Documentation Changes Summary:

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?


 Description   

Our current development, branching, and tagging process only supports working on a single major version (v1.x). To release a new major version (v2.x), we need to determine how to update our branching and development process so that we can continue releasing minor and patch versions for both the v1.x and v2.x Go driver.

Definition of done:

  • Determine and document a new development, branching, and tagging process that supports maintaining both a v1.x and v2.x Go driver.
  • Determine and document a tentative support schedule for the v1.x Go driver.
    • How long will we continue publishing minor versions that support newer versions of the MongoDB server?
    • How long will we continue publishing patch versions with bug fixes for the last supported v1.x minor version(s)?


 Comments   
Comment by Matt Dale [ 17/Apr/23 ]

Resolved with approval of the Go Driver 2.0 scope.

Generated at Thu Feb 08 08:38:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.