Discuss next version to be released

[jackye1995]

Currently I put 0.1.0 as the placeholder for the Spark-Lance connector version.

Looking at https://mvnrepository.com/artifact/com.lancedb/lance-spark, we have released up to 0.25.1, and this is released basically together with lance-core and share the same version.

With the current release strategy, we will not release with name lance-spark, but more detailed names like lance-spark-3.5_2.12. So we have a few options:

1. start with new versioning from 0.1.0
2. continue with the previous versioning, so the next version will be 0.26.0
3. start with a new major version 1.0.0

I am currently preferring option 3, because we want this to be versioned independently from the lance-core version (since they will be released at different cadence), and having a new major version is less confusing than having a new version going back and starting from 0.1.

Thoughts? @SaintBacchus @yanghua

[yanghua]

option 3 lgtm, that means the version of lance-spark will decompile with the version of lance-core?

What's the usage mode for the end users about these two dependencies?

[SaintBacchus]

I chose option 2, but will separate the version of the Spark module in the lance repo from now on.

The old spark module will be frozen, and this repo uses 0.26.0 for the first version.

Is this OK?

[jackye1995]

I think 0.26.0 is already cut in lancedb/lance, but seems like somehow it is not published? https://mvnrepository.com/artifact/com.lancedb/lance-spark

I was under the assumption that lance repo will auto-publish the code to Maven. But if we are not doing that, then option 2 might be fine.

Another factor to consider is backwards compatibility. I am planning to introduce some incompatible changes (draft in #13) based on discussion in lancedb/lance-catalog#9

[westonpace]

0.26.0 is currently released as a pre-release (0.26.0-b1) but there are no stable releases of 0.26.0 yet. Pre-releases are python / rust only so they won't show up in Maven.