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

Proposal: Integrate preview releases in our roadmap/release schedule #96

Open
tomkerkhove opened this issue Mar 21, 2023 · 6 comments
Open

Comments

@tomkerkhove
Copy link
Member

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:

  • Iron out any (obvious) bugs that we have but are not caught by our e2e tests
  • Leverage more stable releases because it was already tested out by the community
  • Provide a simpler way to test upcoming release,s without having to rely on the main image
  • Get feedback faster

However, it should come with the following caveats:

  • It should not introduce (too much) overhead for us (for example, no dedicated doc version?)
  • It does not come with urgent support nor with hotfixes
@tomkerkhove
Copy link
Member Author

Any thoughts @kedacore/keda-maintainers?

@JorTurFer
Copy link
Member

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.

@tomkerkhove
Copy link
Member Author

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"?

@JorTurFer
Copy link
Member

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.
image

There is also another problem with links when you manually introduce the not released version because the menu still points to latest released version:
image

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

image

@tomkerkhove
Copy link
Member Author

Oh I thought we had an "unreleased" or "in development" version, I agree!

@zroubalik
Copy link
Member

Oh I thought we had an "unreleased" or "in development" version, I agree!

I like this approach, to not name it latest but to "unreleased" or "in development".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

3 participants