Skip to content
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

Closed
tomkerkhove opened this issue Jun 20, 2021 · 5 comments · Fixed by #34
Closed

Define a release schedule #24

tomkerkhove opened this issue Jun 20, 2021 · 5 comments · Fixed by #34
Labels
governance All issues related to governance of project release-management

Comments

@tomkerkhove
Copy link
Member

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.

@tomkerkhove tomkerkhove added governance All issues related to governance of project release-management labels Jun 20, 2021
@tomkerkhove
Copy link
Member Author

How does every 2 months sound like?

@zroubalik
Copy link
Member

How does every 2 months sound like?

Can we say some every 2-3 months based on a demand and list of features?

@tomkerkhove
Copy link
Member Author

Sounds good to me, wdyt @jeffhollan @ahmelsayed?

@tomkerkhove
Copy link
Member Author

We should also define why we are using this cycle so end-users get our reasoning.

@jeffhollan
Copy link
Member

Agree on timeline proposed in an effort to provide some predictability to users

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
governance All issues related to governance of project release-management
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants