andygrove opened a new pull request, #114: URL: https://github.com/apache/datafusion-spark/pull/114
## Summary Adds the release process docs and scripts, adapted from `datafusion-sqlparser-rs` for this repo (SPDX headers, two-crate workspace, version tracks the DataFusion major version). - `dev/release/README.md`: the full process. Covers the release PR (version bump, swapping DataFusion git deps for crates.io releases, changelog), RC tagging, tarball creation, the vote, verification, finalizing, publishing to crates.io, cleanup and the announcement. - `generate-changelog.py`: builds the changelog from merged PRs between two refs, using labels and Conventional Commits prefixes. Writes to `dev/changelog/<version>.md`. - `create-tarball.sh`: checks that the tag exists and that its `Cargo.toml` version matches, `git archive`s the tarball, runs RAT on it, signs it, writes checksums, uploads to the svn dev area and prints the vote email. - `verify-release-candidate.sh`: checks the signature and checksums, then runs fmt, build, both test suites, a check that there are no git deps, and `cargo publish --dry-run` in a sandboxed toolchain. - `release-tarball.sh`: moves an approved RC to the svn release area. - `run-rat.sh`: now optionally takes a tarball path so the exact release artifact gets audited. With no arguments it behaves as before, so CI is unchanged. - `.gitignore`: ignores `dev/dist/`. `CONTRIBUTING.md` now links to the release docs. Note: `main` currently depends on DataFusion `branch-56` via git. crates.io rejects git dependencies, so the README makes switching to released DataFusion crates part of the release PR, and the verify script fails if any git deps remain. ## Test plan - [x] `shellcheck` clean on all scripts; `bash -n` / `py_compile` pass - [x] `run-rat.sh <tarball>` on a `git archive` tarball of this branch: 0 unapproved / 0 unknown - [ ] The svn/gpg upload steps will be exercised for real on the first RC 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
