Skip to content

docs(csharp): add C# driver release process#362

Open
eric-wang-1990 wants to merge 6 commits intomainfrom
docs/csharp-release-process
Open

docs(csharp): add C# driver release process#362
eric-wang-1990 wants to merge 6 commits intomainfrom
docs/csharp-release-process

Conversation

@eric-wang-1990
Copy link
Collaborator

Summary

  • Adds csharp/RELEASE_PROCESS.md documenting the release branch model for the C# driver
  • Defines three-phase lifecycle: pre-cutoff (merge from main), cutoff (tag + lock), post-cutoff (cherry-picks only)
  • Covers branch naming, tag conventions, branch protection rules, CI scoping, and consumer mapping

Context

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

  • Review the documented process with the team
  • Validate branch protection rules can be applied to release/csharp/* pattern
  • Confirm CI workflow triggers correctly on release branch pushes

This pull request was AI-assisted by Isaac.

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
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant