[GODRIVER-2978] Automate syncing code between Go driver v1 and v2 Created: 07/Sep/23  Updated: 02/Oct/23  Resolved: 02/Oct/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: Steve Silvester
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: Go Driver 2.0: Driver
Quarter: FY24Q3
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   

While we are developing Go Driver 2.0 and for a period of time after releasing it, we will need to deliver features and fixes to both the Go driver v1 development branch (v1) and v2 development branch (master). To reduce maintenance burden, create an automated process for syncing code between the v1 and v2 branches. For example, a Github workflow that automatically cherry-picks code from one branch to another on PR merge based on something in the PR description.

Open questions:

  • Does Github have some built-in feature that can do this or do we have to build something custom?
  • Is there another project we can use as reference for how to do this?
  • How often do we need to sync code between v1 and v2 development branches?


 Comments   
Comment by Steve Silvester [ 18/Sep/23 ]

https://github.com/mongodb/mongo-go-driver/pull/1391

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