Repository navigation
docs: Update release README examples to 55.2.0 and add SVN commands - #26119
Conversation
…teps - Use 55.2.0 (and branch-55, 55.1.0) in all examples. - Replace the manual version edit and `cargo check -p datafusion` with sed commands and `cargo update --workspace`, plus a check that no reference to the old version is left. - Add `svn ls` checks and commands to `svn export`, verify and unpack the RC and release tarballs.
timsaucer
left a comment
There was a problem hiding this comment.
One minor requested change. Thanks for updating the documentation!
| https://dist.apache.org/repos/dist/release/datafusion/datafusion-54.0.0 \ | ||
| https://dist.apache.org/repos/dist/release/datafusion/datafusion-54.1.0 |
There was a problem hiding this comment.
In general there should only be one prior release if we've been deleting them. I often copy+paste this line so I'd prefer it to only show one.
There was a problem hiding this comment.
Thanks @timsaucer for the review, not sure I'm following, appreciate if you elaborate . I thought we need to remove old prior release with fixes.
Now I can see in svn no last major release, not sure if this is expected

There was a problem hiding this comment.
There was a problem hiding this comment.
The PR is changing the line
svn delete -m "delete old DataFusion release" https://dist.apache.org/repos/dist/release/datafusion/datafusion-50.0.0
to
svn delete -m "delete old DataFusion release" \
https://dist.apache.org/repos/dist/release/datafusion/datafusion-54.0.0 \
https://dist.apache.org/repos/dist/release/datafusion/datafusion-54.1.0
When I've run this command in the past it was helpful to copy & paste this line and edit the version number. I'm guessing when you went through this you needed to delete both 54.0.0 and 54.1.0?
I was just suggesting this be
svn delete -m "delete old DataFusion release" https://dist.apache.org/repos/dist/release/datafusion/datafusion-54.1.0
There was a problem hiding this comment.
Ic, it was an example, let me come up with script then so it would work for any release
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #26119 +/- ##
==========================================
- Coverage 82.73% 82.73% -0.01%
==========================================
Files 1147 1147
Lines 449459 449540 +81
Branches 449459 449540 +81
==========================================
+ Hits 371864 371918 +54
- Misses 54936 54946 +10
- Partials 22659 22676 +17 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
Thanks @timsaucer for the review, I added a small bash command for deletes which prints the |
Which issue does this PR close?
55.2.0(patch) Release (Oct 2026) #25758.Rationale for this change
The release README used 50.x examples and had no commands to check, download or unpack the artifacts in SVN.
What changes are included in this PR?
In
dev/release/README.md:sedandcargo update --workspacecommands for the version and lockfile.svn lschecks after the uploads, andsvn exportplustar xzfcommands for the release tarball.55.0.0in the example) and the releases after it in thereleaseSVN, with a short loop that prints thesvn deletecommands for the other releases.What is the testing strategy for this PR?
Docs only. The
sedcommands reproduce theCargo.tomland docs changes of the 55.2.0 release PR (#26037). The loop was run in bash, zsh and sh against a local SVN repository.Are there any user-facing changes?
No.