-
Notifications
You must be signed in to change notification settings - Fork 492
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
declare a 1.0 release? #290
Comments
I'd love to get the fluent code added. I was planning on updating the PR today the recent code changes and a short discussion of where the bindings are at and future changes/improvements that should probably happen. |
I think we should release a 0.10 with fluent Api and 1.15 bindings before going to 1 I can foresee a few issues poping up from adding fluent bindings and since we plan versionin them together it might give us a small buffer. But can't think of any blockers. |
One more thing is updating the codegen tooling and regenerating api.ts. Last time it caused breaking changes. We could either update swagger-codegen to the latest major, or switch to the openapi-generator. BTW, is the longer term plan to switch to the openapi tooling? |
I also think #53 might be a relevant fix before 1.0 |
We should definitely switch to the openapi-generator.. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle rotten |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
@drubin @silasbw
What are the blockers to a 1.0 release do you think?
Should we try to get the fluent Type/Java Script code added?
Maybe in conjunction with the 1.15 kubernetes API update?
The text was updated successfully, but these errors were encountered: