[DISCUSS] Lower Friction / Lower Ceremony (faster?) releases
- Dominant language
- Rust
- Stars
- 9.3k
- Forks
- 2.4k
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 344
Description
### Is your feature request related to a problem or challenge?
Releasing DataFusion versions is described here:
- https://github.com/apache/datafusion/blob/main/dev/release/README.md
We have been releasing about once a month for the last three years. You can see the history here:
- https://crates.io/crates/datafusion/versions
However, there is some non trivial overhead to doing releases as @findepi has observed, such as the tarball creation and voting process.
Interestingly I believe that one of @jorgecarleitao 's concerns about arrow-rs when he created arrow2 was the (slow) pace of the Apache release model
### Describe the solution you'd like
I would like to discuss what we can do to make releasing easier (and therefore potentially more frequent)
### Describe alternatives you've considered
_No response_
### Additional context
* #13648
Contributor guide
Research direction
Start with dev/release/README.md and compare its described steps with the release history on crates.io. Review the overhead called out in this issue and the discussion in #13648, then identify concrete changes the project could agree on. Done means the release process has an agreed, documented lower-ceremony approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100