andygrove opened a new pull request, #319:
URL: https://github.com/apache/datafusion-spark/pull/319

   ## Which issue does this PR close?
   
   Part of #56. It replaces that issue's plan to make 57.0.0 the first release 
from this repository.
   
   ## Rationale for this change
   
   New Spark-compatible functions and fixes land here between DataFusion major 
releases. Tying `datafusion-spark` releases to DataFusion's would hold them 
back, so this PR proposes releasing 56.x from `main` as often as needed, until 
DataFusion 57.0.0 is released. That only works if `main` doesn't break the 
public API in the meantime, so the policy spells out what counts as a breaking 
change.
   
   ## What changes are included in this PR?
   
   - **`dev/release/README.md`**: expands the Versioning section.
     - The major version matches DataFusion's. Minor releases (such as 56.1.0) 
add functions, features and fixes. Patch releases (such as 56.0.1) contain only 
fixes.
     - `main` stays on DataFusion 56 and releases 56.x until DataFusion 57.0.0 
is released. Then it moves to DataFusion 57, and its next release is 57.0.0.
     - DataFusion 56.0.0 publishes `datafusion-spark` 56.0.0 from `branch-56` 
in apache/datafusion. Later 56.x releases come from this repository, so a 
DataFusion 56.x patch release should not publish `datafusion-spark` again.
     - What a 56.x release must not break, what is allowed, and how to avoid a 
break with `#[deprecated]`. A change to a function's results that makes it 
match Spark counts as a bug fix.
     - Checking a release against the previous one with `cargo-semver-checks`.
   - **`CONTRIBUTING.md`**: a short "API Compatibility" section for 
contributors that links to the policy.
   
   ## Are these changes tested?
   
   Documentation only. To check that the policy can be applied today, I ran 
`cargo semver-checks -p datafusion-spark --all-features` against the crate at 
apache/datafusion's `56.0.0-rc1` tag. Results:
   
   | Compared | Result |
   |---|---|
   | Current `main` | No breaking changes (229 checks pass) |
   | The open cast PRs (#89, #304, #317) | No breaking changes |
   | A test rename of a public function | Reported as a major-version change, 
so the check does detect breaks |
   
   Since rc1, `main` has only added public items, such as `dayname` and 
`date_from_unix_date`.
   
   ## Are there any user-facing changes?
   
   No code changes.
   
   The policy needs agreement with apache/datafusion: its `branch-56` release 
process still runs `cargo publish` for `datafusion-spark`, so DataFusion 56.x 
patch releases would need to stop publishing it after 56.0.0.
   
   _This PR was written by an LLM (Claude) and reviewed before opening._
   
   🤖 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]

Reply via email to