What is a Quarkiverse recommended release lifecycle vs. minors of Quarkus and LTS versions?

[edeweerd1A]

Hi, as maintainer of a Quarkiverse extension, I am asking myself the question what is the recommended release lifecycle. The extension is not included in the quarkus platform, so there is no need to keep up with the pace of Quarkus' releasing. I was wondering what each maintainer is doing out there. What is the typical reaction to a failure of the Quarkus ecosystem CI, identifying a need for a change for compatibility with the latest Quarkus release? Should we do a major release every time that happens? do you do a "release candidate" release, and then do a final actual release only when the LTS comes out? Here you go, I just wanted to have your feedback. Thanks in advance.

[rquinio1A]

I saw https://github.com/quarkiverse/quarkus-openapi-generator was adding -lts in some of their versions (2.14.0-lts & 2.14.0), but it is compiled on non-LTS versions of Quarkus, so it must have another meaning.

[rquinio1A]

IMO one the biggest crietria would be to ease the pick-up / exclusion rules by tooling like Dependabot / RenovateBot / etc.
If someone uses only Quarkus LTS versions, it would be nice to be able to define a rule "only propose version upgrades of quarkiverse extensions compiled on an LTS versions of Quarkus".