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

   ## Which issue does this PR close?
   
   N/A - this is a release process step for the 1.0.0 release.
   
   ## Rationale for this change
   
   The [release 
process](https://github.com/apache/datafusion-comet/blob/main/docs/source/contributor-guide/release_process.md#update-maven-version)
 requires that the Maven version on the release branch is changed from 
`1.0.0-SNAPSHOT` to `1.0.0` before the release candidate is tagged, so that the 
staged Maven artifacts and the source tarball carry the final release version.
   
   This was previously done in #5105, but `branch-1.0` has since been re-cut 
from `main`, so the bump needs to be reapplied.
   
   ## What changes are included in this PR?
   
   - Change the Maven version from `1.0.0-SNAPSHOT` to `1.0.0` in `pom.xml`, 
`common/pom.xml`, `spark/pom.xml`, and `spark-integration/pom.xml`.
   - Update `comet.version` in the Spark test diffs (`dev/diffs/3.4.3.diff`, 
`3.5.9.diff`, `4.0.4.diff`, `4.1.3.diff`).
   - Update the `comet` version in the Iceberg diffs 
(`dev/diffs/iceberg/1.8.1.diff`, `1.9.1.diff`, `1.10.0.diff`, `1.11.0.diff`).
   
   The Rust crate versions in `native/Cargo.toml` are already `1.0.0` and do 
not need to change.
   
   `git grep -n '1.0.0-SNAPSHOT' -- . ':!docs/source/changelog'` now returns no 
hits. The PyArrow UDF jar-resolution fix from #5105 
(`spark/src/test/resources/pyspark/conftest.py`) already landed on `main`, so 
it is not needed here.
   
   ## How are these changes tested?
   
   `./mvnw validate` passes. Otherwise existing CI: the Spark SQL and Iceberg 
test workflows apply the updated diffs and build against the new version, so 
they cover the version references in both the poms and the diff files.
   


-- 
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