-
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
Proposal: Integrate preview releases in our roadmap/release schedule #96
Comments
Any thoughts @kedacore/keda-maintainers? |
I think that we can do it, but I'd like to update the docs to reflect that preview/latest release. For example, the webhook changes required the documentation and we should provide it easily if we want to release previews. |
And what is your concern with our current scenario? Because end-users can already read them? Is it because it does not explicitly say "preview"? |
Currently, we don't have any button to access to unreleased version. If any user wants to check something not released yet in the docs, they need to manually write the next version in the browser bar, which isn't intuitive IMO. There is also another problem with links when you manually introduce the not released version because the menu still points to latest released version: If we release preview versions, I'd like to have something more user-friendly to browse those features. For example, ArgoCD documentation has an option in the version selector for that and it's so much user-friendly because they can select it just clicking |
Oh I thought we had an "unreleased" or "in development" version, I agree! |
I like this approach, to not name it |
I'd like to propose to integrate a single preview releases in our roadmap/release schedule 1/1.5mo before every official release that we are planning.
This would allow us to:
However, it should come with the following caveats:
The text was updated successfully, but these errors were encountered: