-
Notifications
You must be signed in to change notification settings - Fork 706
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
Add "not maintained" notice to other operator repos #1423
Comments
SGTM. |
sounds good. Let's hold this task until we officially release the repo |
Can we move forward? |
Yes, I think so. I'll start adding notices. |
+1 to this. There are issues created in other repos even now |
Should we archive repos as well (with notice in Readme)? |
Let me update the README and then comment in kubeflow/community#479 to see if we can include those repos as part of the archiving process. @kubeflow/wg-training-leads Let me know if there are any concerns for archiving (pytorch, xgboost, mxnet). |
Thanks for driving the efforts. It sounds good to me. Let's give the notice and archive them later. |
Notices were added and I commented on the issue to archive the repos. Let's track the progress there. |
We should add notice to all other operator repos and freeze code changes. Let's use this issue to discuss the wording before adding the notice to the top of the README files in those repos.
/cc @kubeflow/wg-training-leads
The text was updated successfully, but these errors were encountered: