volcano
volcano copied to clipboard
volcano-sh
We should recall `api` package back to `volcano` repo
Why is this needed:
We have separated the api package from the main repo. #1401
But it will bring some difficulties to development
e.g.
If I want to add some experiment fields to api, I must submit a pr to api repo first.
But an experiment idea shouldn't be merged into the main thread before it is mature.
What would you like to be added:
Maybe we can still keep api package in volcano repo and sync this sub package to its own repo (like what Kubernetes did)
But an experiment idea shouldn't be merged into the main thread before it is mature.
That should be ok for alpha, beta and GA feature.
Hello 👋 Looks like there was no activity on this issue for last 90 days. Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗 If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
@hwdef Can you help for that?
Yes, I can work on it. But a robot may be needed to synchronize the two repo, I don’t know how to deal with it
Maybe we can still keep api package in volcano repo and sync this sub package to its own repo (like what Kubernetes did)
That's better to me :)
Hello 👋 Looks like there was no activity on this issue for last 90 days. Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗 If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).
Closing for now as there was no activity for last 60 days after marked as stale, let us know if you need this to be reopened! 🤗
Hello 👋 Looks like there was no activity on this issue for last 90 days. Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗 If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).
Hello 👋 Looks like there was no activity on this issue for last 90 days. Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗 If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).
Hello 👋 Looks like there was no activity on this issue for last 90 days. Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗 If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).
Hello 👋 Looks like there was no activity on this issue for last 90 days. Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗 If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).
Can we include this in the next release cycle?
We can have staging/ folder under the v/v and sync content to v/api
Can we include this in the next release cycle? We can have
staging/folder under the v/v and sync content to v/api
we need a robot to sync v/v/staging to v/api.