generated from kedacore/github-template
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Define a release schedule #24
Labels
Comments
How does every 2 months sound like? |
1 task
Can we say some every 2-3 months based on a demand and list of features? |
Sounds good to me, wdyt @jeffhollan @ahmelsayed? |
We should also define why we are using this cycle so end-users get our reasoning. |
Agree on timeline proposed in an effort to provide some predictability to users |
This was referenced Oct 20, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As an end-user it is easier if we would have a release schedule and ship every X period. This would allow them to more easily plan upgrades which would help maintainers to focus on more recent versions.
This issue is here for us to discuss if that makes sense for KEDA and what our cycles would look like.
The text was updated successfully, but these errors were encountered: