Shared library for redistribution

[Kreijstal]

Any plans of tagging releases of this?

[ggerganov]

Definitely will start versioning and tagging. Still figuring out the details and hope to set this in action soon.

[JohannesGaessler]

How strict would versioning be regarding breaking changes?

[slaren]

We should use semantic versioning to indicate breaking changes.

[JohannesGaessler]

What I mean is: do we count all headers and modules for when to increment versions? The core ggml interface is I think relatively mature and I don't expect a lot of breaking changes. But for the training code in particular I think there will still be a lot of changes. Should we increment the overall ggml version to indicate a breaking change in that scenario or should we define breaking changes to only count depending on whether a specific part of the library is considered to be stable?

[slaren]

I don't think there are any specific plans about how to implement this. I guess at least we will need to make a new release when features are added to ggml that are used in llama.cpp or whisper.cpp, since one of the goals is being able to use the same libraries for both of these projects, as well as possibly other projects such as sd.cpp, if they choose to use the versioned libraries. So we will probably need to tag a new release and bump the major version even for incompatible changes to experimental features, if these are used in llama.cpp. That should be fine though.