Hi Yun, Your proposal LGTM.
However, regarding compatibility, I think this information has to be tracked regardless of the release cycle, because users can mix different client / server versions in their environments. Cheers, Dmitri. On Tue, Mar 25, 2025 at 5:01 PM yun zou <yunzou.colost...@gmail.com> wrote: > Hi Team, > > Given that we are now introducing Spark Client, one thing we need to decide > is the release cycle for the Spark Plugin. > > I propose to bundle the client release with Polaris main release like > Iceberg. In that way, users will be able to get the client support for new > APIs in the same release, and version compatibility is also implicitly > implied in the release. > > An alternative is to release the client independently like > spark-cassandra-connector. In that case, the client will not have to do > extra release if there is no server API change. The drawback is that the > client release will need to start after the server release is finished in > case there are new changes, and extra Compatible Version information needs > to be published to help users understand the compatibility. > > Please let me know about your thoughts on the client release cycles. > > Best Regards, > Yun >
