andygrove opened a new issue, #31: URL: https://github.com/apache/datafusion-iceberg/issues/31
### Is your feature request related to a problem or challenge? This repository was split out of apache/iceberg-rust. That project's release tooling lives at the repository level, so it didn't move with the crate. As a result, there's currently no way to produce an ASF source release: - no scripts to create, verify and publish a release candidate - no Apache RAT license audit, locally or in CI - no changelog generation - no documented release process The published crate also wouldn't include `LICENSE` or `NOTICE`, because the per-crate symlinks were removed in #2. ### Describe the solution you'd like Add a `dev/release/` directory modelled on the other DataFusion subprojects (e.g. apache/datafusion-ballista): - `README.md` describing the release process - `create-tarball.sh`, `verify-release-candidate.sh` and `release-tarball.sh` - `generate-changelog.py` - `run-rat.sh`, `check-rat-report.py` and `rat_exclude_files.txt`, plus a RAT job in CI Also restore `LICENSE` and `NOTICE` in the published crate. ### Additional context Two other things block publishing to crates.io: - The crate name: see #30. - `iceberg` is a git dependency. `cargo publish` requires a crates.io version, and the latest `iceberg` release (0.10.1) lacks APIs this crate uses (`with_encryption_manager`, `calc_min_compatible_format`). The first release therefore depends on the next iceberg-rust release. -- 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]
