Reduce the release cycle?

[zroubalik]

KEDA has matured significantly over the years, so our current pace of 4 releases a year may no longer be necessary. With fewer major features in each release, I’d like to propose moving to 2–3 releases annually. This should reduce the burden on maintainers who handle the release process and lessen the update frequency for end users.

Alongside this change, we can also look into improving our overall release process, including more targeted patch releases where needed—while still being mindful not to overload our release schedule.

I’d love to hear everyone’s thoughts and suggestions on these ideas.
Thank you!

[tomkerkhove]

I think this makes sense

[JorTurFer]

I support this idea because we have reached a moment when the new features cadence has decreased, but I think that we could try to take this fact as a good reason to ship a patch releases every month or so. I'd say that we could create more automations around the release process to simplify the patch release process.

My proposal is to ship 2-3 versions per year (every 4-6 months) and a patch release automatically every month, supporting only the last 2 versions if we can achieve an easy and semi-automated release process (so actually, it0ll mean 2 patch releases per month, one per version)