Release Cycle of llama.cpp

[yavornenov-ost]

Hi,

I'm looking into using the llama.cpp library and would like to better understand the project's release cycle. From what I can tell, the project doesn’t follow traditional release practices, as multiple releases can be published in a single day.

• Is there a notion of a "stable" release?
• More generally, is there any documentation or information available that describes the release cycle?

Thanks in advance!

With kind regards,
Yavor

[ggerganov]

Is there a notion of a "stable" release?

Not atm.

More generally, is there any documentation or information available that describes the release cycle?

No, we haven't put much effort into that. But it's something we should address soon.

We can start tagging certain versions as stable. The thing that is not clear to me is how to decide which versions to tag. The project is developing very fast, so it is difficult to decide when we have a stable release. Any suggestions?

[yavornenov-ost]

Thank you for the quick response, @ggerganov.

I appreciate the difficulty in establishing a formal release policy for dynamic open-source projects like llama.cpp. I don’t have direct experience with open-source governance to add much beyond the obvious here, but from a user’s perspective, a useful alternative to stable releases could be clearer differentiation between stable and experimental features/APIs, which might be easier to achieve.

Kudos to the team for the excellent work!