docs(csharp): add C# driver release process#362
Open
eric-wang-1990 wants to merge 14 commits intomainfrom
Open
docs(csharp): add C# driver release process#362eric-wang-1990 wants to merge 14 commits intomainfrom
eric-wang-1990 wants to merge 14 commits intomainfrom
Conversation
Defines the release branch lifecycle (pre-cutoff, cutoff, post-cutoff), tag conventions, branch protection rules, and CI scoping for C# releases. Co-authored-by: Isaac
Co-authored-by: Isaac
Release branches follow the same rules as main (PR required, CI must pass). Cutoff is enforced by convention, not extra restrictions. Co-authored-by: Isaac
Replace gitGraph with flowchart to avoid "Cannot merge branch into itself" rendering error on GitHub. Co-authored-by: Isaac
The ADBC driver version appears in Databricks query history, enabling issue investigation by driver version. Co-authored-by: Isaac
Co-authored-by: Isaac
Co-authored-by: Isaac
davidhcoe
reviewed
Mar 24, 2026
csharp/RELEASE_PROCESS.md
Outdated
|
|
||
| - All new commits go to `main` as usual. | ||
| - The release branch is created early from `main`. | ||
| - Periodically merge `main` into the release branch to keep it current. |
Collaborator
There was a problem hiding this comment.
Why would we do it this way instead of just creating a release branch when one is ready?
Collaborator
Author
There was a problem hiding this comment.
Good point — simplified. The doc now branches directly off main at release time with no pre-cutoff phase. The three-phase model was over-engineered for how we'll actually work.
eric-wang-1990
commented
Mar 29, 2026
csharp/RELEASE_PROCESS.md
Outdated
| 1. Final merge of `main` into the release branch | ||
| 2. Tag the cutoff commit (e.g., `csharp/v1.1.0`) | ||
| 3. Update `stable/csharp` to point to this tag | ||
| 4. Create the next release branch (e.g., `release/csharp/v1.2.0`) immediately, to give the team a landing place for new work |
Collaborator
Author
There was a problem hiding this comment.
Do you need create next? If we are only cutting off the release branch when we are about to release, it seems unnecessary
Collaborator
Author
There was a problem hiding this comment.
Agreed, removed. The doc no longer creates the next release branch at cutoff — branches are created only when ready to release.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
csharp/RELEASE_PROCESS.mddocumenting the release branch model for the C# driverContext
The C# driver needs a release branch model so downstream consumers (e.g., PowerBI) can pin to stable versions and receive hotfixes without pulling in all new development work. Go already uses tag-only releases; this introduces release branches specifically for C#.
Test plan
release/csharp/*patternThis pull request was AI-assisted by Isaac.