comphead opened a new pull request, #26119: URL: https://github.com/apache/datafusion/pull/26119
## Which issue does this PR close? - Related to #25758 (the 55.2.0 release, where these gaps were found). ## Rationale for this change While running the 55.2.0 release, the release README still used 50.x examples and a few steps had no commands: - The version bump asked for a manual edit of the root `Cargo.toml` and a `cargo check -p datafusion` to refresh `Cargo.lock`. - Nothing showed how to check the artifacts in SVN after uploading them. - "Download and unpack the official release tarball" had no commands. ## What changes are included in this PR? Only `dev/release/README.md`: - Use 55.2.0 (with `branch-55` and `55.1.0` as the previous release) in all examples. - Step 2: add `sed` commands for the version in `Cargo.toml` and the four docs files, `cargo update --workspace` for `Cargo.lock`, and a `git grep` check that no reference to the old version is left. - Add `svn ls` checks for SVN access, after `create-tarball.sh` and after `release-tarball.sh`. - Steps 7 and 10: add commands to `svn export` the RC or the release, verify the signature and checksums, and unpack the tarball. ## What is the testing strategy for this PR? Docs only. `ci/scripts/doc_prettier_check.sh`, `ci/scripts/rust_fmt.sh` and `typos` pass. The `sed` commands reproduce the `Cargo.toml` and docs changes of the 55.2.0 release PR (#26037) byte for byte. The `svn export`, checksum and unpack commands were run against a local SVN repository holding the 55.2.0 RC artifacts. The `gpg` lines were not run. ## Are there any user-facing changes? No. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
