Add release management page to the documentation#21001
Merged
alamb merged 7 commits intoapache:mainfrom Apr 15, 2026
Merged
Conversation
alamb
commented
Mar 17, 2026
|
|
||
| ## Release Process Overview | ||
|
|
||
| New development happens on the `main` branch. |
Contributor
Author
There was a problem hiding this comment.
I moved this comment into a new page on the doc site for more visibility
comphead
reviewed
Mar 17, 2026
|
|
||
| ## Backport Workflow | ||
|
|
||
| The usual workflow is: |
Contributor
There was a problem hiding this comment.
from my experience if backport(s) happened, should we also create a new tag, new RC and new voting process?
Contributor
There was a problem hiding this comment.
and also update the change lists
Contributor
Author
There was a problem hiding this comment.
I tried to add this information to dev/release/README.md and cleaned it up -- does that make sense?
github-actions
Bot
added
the
development-process
5 tasks
Contributor
Author
I think that is a great idea (I have had good luck automating a bunch of the release management stuff too) |
Rich-T-kid
pushed a commit
to Rich-T-kid/datafusion
that referenced
this pull request
Apr 21, 2026
## Which issue does this PR close? - Related to apache#19692 ## Rationale for this change As we see more people helping with releases (thank you @timsaucer and @comphead ❤️ ) I think having the process documented more will help Also, I spent quite a while back porting PRs and wanted to document it better ## What changes are included in this PR? 1. Add a release management page 2. Leave links to relevant sections ## Are these changes tested? By CI ## Are there any user-facing changes? Docs only
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.
Which issue does this PR close?
53.0.0(Feb 2026 / Mar 2026) #19692Rationale for this change
As we see more people helping with releases (thank you @timsaucer and @comphead ❤️ ) I think having the process documented more will help
Also, I spent quite a while back porting PRs and wanted to document it better
What changes are included in this PR?
Are these changes tested?
By CI
Are there any user-facing changes?
Docs only