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

declare a 1.0 release? #290

Open
brendandburns opened this issue Jun 25, 2019 · 10 comments
Open

declare a 1.0 release? #290

brendandburns opened this issue Jun 25, 2019 · 10 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@brendandburns
Copy link
Contributor

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

@silasbw
Copy link
Contributor

silasbw commented Jun 25, 2019

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.

@drubin
Copy link
Contributor

drubin commented Jun 25, 2019

I think we should release a 0.10 with fluent Api and 1.15 bindings before going to 1
0

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.

@silasbw
Copy link
Contributor

silasbw commented Jun 25, 2019

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?

@drubin
Copy link
Contributor

drubin commented Jun 25, 2019

I also think #53 might be a relevant fix before 1.0

@brendandburns
Copy link
Contributor Author

We should definitely switch to the openapi-generator..

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 25, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 25, 2019
@drubin
Copy link
Contributor

drubin commented Oct 25, 2019

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Oct 25, 2019
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 23, 2020
@drubin
Copy link
Contributor

drubin commented Jan 23, 2020

/remove-lifecycle stale
/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

5 participants