andygrove opened a new pull request, #4324:
URL: https://github.com/apache/datafusion-comet/pull/4324
## Which issue does this PR close?
Closes #4317.
## Rationale for this change
Comet has no documented versioning policy. New users and downstream
projects have no way to know what compatibility guarantees a Comet
release provides, how often releases ship, which Spark patches are
supported, or what 1.0 will mean. This PR adds an initial policy
modeled on Apache Spark's, adapted to Comet's pre-1.0 status and
faster release cadence.
## What changes are included in this PR?
- New page `docs/source/about/versioning_policy.md` covering:
- Pre-1.0 release model: minors may break, patches are bug-fix only.
- Items explicitly not stable in 0.x: `spark.comet.*` configs, the
protobuf plan format, and internal APIs.
- Compatibility commitments that apply even in 0.x: public Scala and
Java API source/binary compatibility across patch releases with a
one-minor deprecation cycle before removal (with an exception for
a future `@Unstable` annotation), and query result semantics for
expressions and operators marked `Compatible`.
- Apache Spark version support: each Comet release tracks the latest
patch of every supported Spark minor; dropping a Spark minor is
pre-announced one Comet minor in advance.
- Release cadence: 0.X.0 minors every four to six weeks; patches on
demand for the latest minor only.
- Native library coupling between the JVM jar and the native lib.
- Road to 1.0 and LTS, linking to #4082 for 1.0 planning.
- `docs/source/about/index.md` toctree updated to include the new page.
## How are these changes tested?
Documentation-only change. Sphinx will build the new page on CI as
part of the existing docs build.
---
Drafted with the help of the `superpowers:brainstorming` skill.
--
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]
