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

v1alpha3 planning #27

Open
ffromani opened this issue Feb 1, 2023 · 3 comments
Open

v1alpha3 planning #27

ffromani opened this issue Feb 1, 2023 · 3 comments

Comments

@ffromani
Copy link
Contributor

ffromani commented Feb 1, 2023

Once #24 is done, do we want or need another v1alpha version or should we jump to v1beta1?

This issue is meant to track the requirements and the planning for v1alpha3

@swatisehgal
Copy link
Contributor

If we identify items down the line that justify the need for v1alpha3we can move to the next alpha version but at this point, I think we should directly aim to move to v1beta1.

@ffromani
Copy link
Contributor Author

ffromani commented Feb 1, 2023

If we identify items down the line that justify the need for v1alpha3we can move to the next alpha version but at this point, I think we should directly aim to move to v1beta1.

I fully agree. I filed this issue mostly for due diligence, but I'm also convinced v1beta1 is the next logical step.

@fmuyassarov
Copy link

@ffromani are you planning to cut a release for v1alpha2?

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

No branches or pull requests

3 participants