QLever Stable Releases?

[ahankinson]

It's great to see QLever being so actively developed!

However, we've been bitten a couple times by updates that broke something fundamental. We are still in pre-production for our service, so it's not a huge deal, but in thinking about our roadmap, it would be great to know it there was a "stable" channel we could follow.

Is there a plan for some form of "stable / develop" branch split, or tagged releases in GitHub? It doesn't really matter what they're called, or the frequency at which the "stable" versions are published, but some form of release management with a tagged version would be helpful. (Otherwise we have to rely on the GitHub SHAs for knowing, specifically, which version is running.)

Many thanks for building this amazing tool.

[WolfgangFahl]

Definitly LTS versions are a must feature for a product. QLever is fortunately on the way to being a product. To get there this is a major step.

[ktk]

This is on the roadmap for later this year. And kind of financial support for efforts like this is greatly appreciated.