search

kubeflow / website

Kubeflow Website
https://www.kubeflow.org
Creative Commons Attribution 4.0 International
150 stars 777 forks source link

[DOCS] - "Outdated" files (38/250) #2177

Open rui-vas opened 4 years ago

rui-vas commented 4 years ago

Below is a list of all the outdated files on the docs today.

There are 120 files with "Out of date" out of the 250 files under /content/en/docs/:

./components/central-dash/overview.md
./components/central-dash/registration-flow.md
./components/fairing/configure-fairing.md
./components/fairing/fairing-overview.md
./components/fairing/gcp/configure-gcp.md
./components/fairing/gcp/tutorials/gcp-kubeflow-notebook.md
./components/fairing/gcp/tutorials/gcp-local-notebook.md
./components/fairing/install-fairing.md
./components/fairing/reference/sdk.md
./components/fairing/tutorials/other-tutorials.md
./components/feature-store/getting-started.md
./components/feature-store/overview.md
./components/jupyter.md
./components/misc/nuclio.md
./components/multi-tenancy/design.md
./components/multi-tenancy/getting-started.md
./components/multi-tenancy/overview.md
./components/serving/bentoml.md
./components/serving/tfbatchpredict.md
./components/serving/tfserving_new.md
./components/serving/tritoninferenceserver.md
./components/training/chainer.md
./components/training/mpi.md
./components/training/mxnet.md
./components/training/pytorch.md
./components/training/tftraining.md
./examples/blog-posts.md
./examples/codelabs-tutorials.md
./examples/kubeflow-samples.md
./examples/shared-resources.md
./examples/videos.md
./gke/anthos.md
./gke/cloud-filestore.md
./gke/custom-domain.md
./gke/customizing-gke.md
./gke/deploy/monitor-iap-setup.md
./gke/gcp-e2e.md
./gke/monitoring.md
./gke/pipelines/enable-gpu-and-tpu.md
./gke/pipelines/preemptible.md
./gke/private-clusters.md
./gke/troubleshooting-gke.md
./ibm/existing-cluster.md
./ibm/iks-e2e.md
./notebooks/custom-notebook.md
./notebooks/setup.md
./notebooks/submit-docker-image.md
./notebooks/submit-kubernetes.md
./notebooks/troubleshoot.md
./notebooks/why-use-jupyter-notebook.md
./openshift/install-kubeflow.md
./openshift/uninstall-kubeflow.md
./other-guides/freq-ask-questions.md
./other-guides/integrations/data-management.md
./other-guides/istio-in-kubeflow.md
./other-guides/job-scheduling.md
./other-guides/kubeflow-on-multinode-cluster.md
./other-guides/troubleshooting.md
./other-guides/usage-reporting.md
./pipelines/caching.md
./pipelines/overview/concepts/component.md
./pipelines/overview/concepts/experiment.md
./pipelines/overview/concepts/graph.md
./pipelines/overview/concepts/output-artifact.md
./pipelines/overview/concepts/pipeline.md
./pipelines/overview/concepts/run-trigger.md
./pipelines/overview/concepts/run.md
./pipelines/overview/concepts/step.md
./pipelines/overview/interfaces.md
./pipelines/overview/pipelines-overview.md
./pipelines/pipelines-quickstart.md
./pipelines/reference/component-spec.md
./pipelines/reference/sdk.md
./pipelines/sdk/best-practices.md
./pipelines/sdk/build-component.md
./pipelines/sdk/component-development.md
./pipelines/sdk/dsl-recursion.md
./pipelines/sdk/enviroment_variables.md
./pipelines/sdk/gcp.md
./pipelines/sdk/install-sdk.md
./pipelines/sdk/lightweight-python-components.md
./pipelines/sdk/manipulate-resources.md
./pipelines/sdk/output-viewer.md
./pipelines/sdk/parameters.md
./pipelines/sdk/pipelines-metrics.md
./pipelines/sdk/python-based-visualizations.md
./pipelines/sdk/sdk-overview.md
./pipelines/sdk/static-type-checking.md
./pipelines/troubleshooting.md
./pipelines/tutorials/api-pipelines.md
./pipelines/tutorials/build-pipeline.md
./pipelines/tutorials/cloud-tutorials.md
./pipelines/tutorials/sdk-examples.md
./reference/images.md
./reference/mpijob/v1alpha2/mpi.md
./reference/overview.md
./reference/pytorchjob/v1/pytorch.md
./reference/pytorchjob/v1beta2/pytorch.md
./reference/tfjob/v1/common.md
./reference/tfjob/v1/tensorflow.md
./reference/tfjob/v1beta2/common.md
./reference/tfjob/v1beta2/tensorflow.md
./reference/version-policy.md
./started/cloud/getting-started-aws.md
./started/cloud/getting-started-azure.md
./started/cloud/getting-started-gke.md
./started/getting-started.md
./started/k8s/kfctl-existing-arrikto.md
./started/k8s/kfctl-istio-dex.md
./started/k8s/kfctl-k8s-istio.md
./started/k8s/overview.md
./started/kubeflow-overview.md
./started/workstation/getting-started-linux.md
./started/workstation/getting-started-macos.md
./started/workstation/getting-started-minikf.md
./started/workstation/getting-started-multipass.md
./started/workstation/getting-started-windows.md
./started/workstation/minikf-gcp.md
./started/workstation/minikube-linux.md
./upgrading/upgrade.md
issue-label-bot[bot] commented 4 years ago

Issue-Label Bot is automatically applying the labels:

Label Probability
area/docs 0.79
kind/bug 0.55

Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback! Links: app homepage, dashboard and code for this bot.

rui-vas commented 4 years ago

@8bitmp3 @jlewi @Bobgy @joeliedtke @rmgogogo

I compiled this list of outdated docs. I did this 3 days ago, but only thought of pinging you now. Let me know how we can effectively tackle this issue 🚀

rmgogogo commented 4 years ago

Thanks Rui. Would you share how to check it's "outdated" here? I may have less knowledge on it.

Do you mean compare it with the website and website doesn't have the latest content in Github?

jlewi commented 4 years ago

Thanks @RFMVasconcelos

Can we identify the owners for the relevant docs and file issues for them to update the docs? Maybe you can automate the opening of GitHub issues using the GitHub CLI/API?

For locations with outdated or no OWNERs files can we try to track down the appropriate owners or WG?

jbottum commented 4 years ago

@cspavlou @kimwnasptd @andreyvelich @james-jwu HI All, it appears that the docs are out of date for several components. Can we please try to get those updated by the end of October ?

8bitmp3 commented 4 years ago

cc fyi @RFMVasconcelos @alfsuse @Jeffwan @neuromage @numerology @vpavlin @crobby @pdmack @shawnzhu @adrian555 @Tomcli

jlewi commented 4 years ago

@jbottum @8bitmp3 @RFMVasconcelos thanks for driving this. If we want this to get fixed I think we need to

  1. Create accountability
  2. Create urgency

WGs and OWNERs files should solve the first problem.

Any ideas how we can create urgency? Do we need to establish of deleting docs older than X?

alfsuse commented 4 years ago

@jbottum @8bitmp3 @RFMVasconcelos thanks for driving this. If we want this to get fixed I think we need to

  1. Create accountability
  2. Create urgency

WGs and OWNERs files should solve the first problem.

Any ideas how we can create urgency? Do we need to establish of deleting docs older than X? How about open a PR and pin it at the top of the PR page with the disclaimer that if the author or anyone else will not update the docs before a certain date (end of October) the pages will be deleted?

how about update the list @RFMVasconcelos put together with the owner's name for each page? This way we will know who is working on what.

One important point I think we should pay attention to the sections root pages.. those shouldn't be deleted in any case

for the Workstation sections, I may work on the minikube pages and general ones.

rui-vas commented 4 years ago

Updated List - 106 out of 250 docs files are "Outdated"

Split by section:

rui-vas commented 4 years ago

@jlewi @8bitmp3 @jbottum please find above the updated "outdated docs" list, by section of the website.

  1. Accountability:

    It seems that we're missing owners for Components (partial), Examples, and Notebooks.

  2. Urgency:

    As we struggle with limited capacity, I would suggest we specify priorities per OWNER. Maybe have OWNERS create an issue with their list of priorities and delivery predictions?

WDYT?

8bitmp3 commented 4 years ago

A relevant thread about the Upgrading section from https://github.com/kubeflow/website/pull/2257#issuecomment-703977899 by @jlewi

@8bitmp3 should we just delete these pages? https://www.kubeflow.org/docs/upgrading/upgrade/

These docs no longer looks relevant.

@jlewi If you're OK with removing the whole section, we can do that (cc @RFMVasconcelos ). Then we together with OWNERS of each of the "subprojects" (AWS, IBM Cloud, Azure, Pipelines, etc) can start adding an upgrading-kubeflow.md to their directories. WDYT?

cc @Bobgy @joeliedtke

From OWNERS files:

Other components...

joeliedtke commented 4 years ago

I like the idea of regularly reviewing our docs, but I’m concerned that tagging each doc as outdated creates unnecessary toil for docs contributors. Are there any other docs projects that you know of that use this strategy? If so, what was their experience like?

WGs should be updating docs as a part of their work. This leads me to wonder, how much of the docset is expected to go stale with each release? If the WGs are updating their docs, then only a small portion of the docset should reasonably break in a release. Assuming that this is correct, the time spent checking docs may not feel worthwhile for contributors since they may test many pages without finding an issue. Testing a document like a tutorial is resource intensive. If contributors are asked to commit time to a task that does not seem sufficiently impactful, they may not participate or they may work around the system. (By writing a script to remove the tag.)

Perhaps we should address this issue in two ways. First, get each WG to review their docs once to verify that they currently have docs that work as expected. Second, going forward we could surface information to get reactive participation from the WGs. We could provide a report that links docs bugs to docs, so owners can respond to user feedback. We could also look at setting Kubeflow.org up to automatically add a “This page might be broken” link to docs with open issues. These links could open a GitHub issues query filtered to that doc’s issues.

That approach gives users insight into what may be broken, and ensures that WGs are aware of the issues that are reported for their docs. What do you think?

woop commented 4 years ago

Can somebody explain how docs that were written for Kubeflow 1.1 (feature store) are flagged as outdated? They shouldn't even be visible in 1.0 and yet that is what the pages now show.

PatrickXYS commented 4 years ago

/reopen

k8s-ci-robot commented 4 years ago

@PatrickXYS: Reopened this issue.

In response to [this](https://github.com/kubeflow/website/issues/2177#issuecomment-704735945): >/reopen Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
8bitmp3 commented 4 years ago

Thank you so much for your awesome feedback @joeliedtke

Perhaps we should address this issue in two ways. First, get each WG to review their docs once to verify that they currently have docs that work as expected. Second, going forward we could surface information to get reactive participation from the WGs. We could provide a report that links docs bugs to docs, so owners can respond to user feedback. We could also look at setting Kubeflow.org up to automatically add a “This page might be broken” link to docs with open issues. These links could open a GitHub issues query filtered to that doc’s issues.

That approach gives users insight into what may be broken, and ensures that WGs are aware of the issues that are reported for their docs. What do you think?

💯% @joeliedtke 👍 👍 👍

What are your thoughts @PatrickXYS@adrian555 @animeshsingh @Tomcli @IronPan @numerology @neuromage @alfsuse @Jeffwan @aronchik @shawnzhu @rmgogogo @cliveseldon @knkski (and many more 😃 ) ?

Hi @woop! I think the docs were flagged as "outdated" during the v1.1 docs transition. Check out @jlewi and @RFMVasconcelos 's comments here: https://github.com/kubeflow/website/issues/1984#issuecomment-651421190 and https://github.com/kubeflow/website/issues/1984#issuecomment-661925946 I hope this helps!

alfsuse commented 4 years ago

First, get each WG to review their docs once to verify that they currently have docs that work as expected. Second, going forward we could surface information to get reactive participation from the WGs. I agree with @joeliedtke comment above but so I wonder do we have a WG for each section? I'm not aware of a WG for the "local/workstation" sections as an example.. should we create one?

I think we should put in place a process where each WG before any new release takes a review in advance so we know upfront which page needs to be re-worked and which not.

Also on another note: Do we need a documentation lifecycle? Like, evaluate if a section/page is still useful over time and eventually remove it so as to maintain the overall documentation more "light".

joeliedtke commented 4 years ago

Regarding adding a documentation lifecycle, that may be a good question to discuss in a community meeting. My initial thought is that we probably don't need full documentation reviews for minor releases. A full review may be more appropriate for a major release, since there is more potential for a breaking change.

Bobgy commented 4 years ago

With current pace Kubeflow is evolving, a lot of docs become outdated even between minor releases. When looking at pipelines docs, there's really a lot I found, so I think it's a valuable process we can leverage

8bitmp3 commented 4 years ago

When looking at pipelines docs, there's really a lot I found

@Bobgy Any particular KFP ones that stood out and require an urgent refresh?

Bobgy commented 4 years ago

I'm collecting KFP doc updates and triage in https://github.com/kubeflow/pipelines/issues/4324

8bitmp3 commented 4 years ago

fyi Update to OWNERS

  • Azure docs/azure: @aronchick

Both @eedorenko and @sudivate are also part of the Azure group 👍

cc @RFMVasconcelos

rui-vas commented 4 years ago

Update - 69 out of 250 files "outdated"

Hey everyone!

Following the last community meeting, here is an update on docs. We are making progress. From 120, we're now at 69 outdated pages. 🚀

We have also cleared the Getting Started and Overview pages, which, even if not perfect yet, do not appear "outdated" to new-comers anymore.

Tagging OWNERS of respective docs here so we can get that down to zero soon 🚀

cc @8bitmp3 @jbottum @jlewi @joeliedtke @Bobgy @alfsuse @woop @animeshsingh

Outdated pages

Getting started:

content/en/docs/started/workstation/getting-started-minikf.md
content/en/docs/started/workstation/minikf-gcp.md
content/en/docs/started/k8s/kfctl-existing-arrikto.md
content/en/docs/started/cloud/getting-started-aws.md
content/en/docs/started/cloud/getting-started-azure.md

@jbottum for arrikto/minikf docs @Jeffwan @PatrickXYS for AWS @aronchick @eedorenko @sudivate for Azure

Pipelines:

content/en/docs/pipelines/caching.md
content/en/docs/pipelines/troubleshooting.md
content/en/docs/pipelines/pipelines-quickstart.md
content/en/docs/pipelines/sdk/dsl-recursion.md
content/en/docs/pipelines/sdk/best-practices.md
content/en/docs/pipelines/sdk/output-viewer.md
content/en/docs/pipelines/sdk/component-development.md
content/en/docs/pipelines/sdk/pipelines-metrics.md
content/en/docs/pipelines/sdk/build-component.md
content/en/docs/pipelines/sdk/manipulate-resources.md
content/en/docs/pipelines/sdk/enviroment_variables.md
content/en/docs/pipelines/reference/component-spec.md
content/en/docs/pipelines/reference/sdk.md

OWNERS: @Bobgy @IronPan @neuromage @Ark-kun @numerology @joeliedtke @alfsuse

Components:

content/en/docs/components/misc/nuclio.md
content/en/docs/components/serving/tritoninferenceserver.md
content/en/docs/components/serving/bentoml.md
content/en/docs/components/serving/tfbatchpredict.md
content/en/docs/components/serving/tfserving_new.md
content/en/docs/components/multi-tenancy/design.md
content/en/docs/components/training/mpi.md
content/en/docs/components/training/pytorch.md
content/en/docs/components/training/chainer.md
content/en/docs/components/training/tftraining.md
content/en/docs/components/training/mxnet.md
content/en/docs/components/jupyter.md
content/en/docs/components/central-dash/overview.md
content/en/docs/components/central-dash/registration-flow.md
content/en/docs/components/feature-store/overview.md
content/en/docs/components/feature-store/getting-started.md
content/en/docs/components/fairing/install-fairing.md
content/en/docs/components/fairing/configure-fairing.md
content/en/docs/components/fairing/tutorials/other-tutorials.md
content/en/docs/components/fairing/fairing-overview.md
content/en/docs/components/fairing/reference/sdk.md

OWNERS: @woop for components/feature-store @adrian555 @animeshsingh @cliveseldon @ellistarn @ryandawsonuk @Tomcli @yuzisun for components/serving

WITH NO OWNERS file:

components/fairing components/misc components/multi-tenancy components/central-dash

Is there anyone/SIG/WG who qualifies to lead these docs?

GKE:

content/en/docs/gke/gcp-e2e.md
content/en/docs/gke/customizing-gke.md
content/en/docs/gke/troubleshooting-gke.md
content/en/docs/gke/custom-domain.md
content/en/docs/gke/deploy/monitor-iap-setup.md
content/en/docs/gke/anthos.md
content/en/docs/gke/pipelines/enable-gpu-and-tpu.md
content/en/docs/gke/pipelines/preemptible.md
content/en/docs/gke/cloud-filestore.md
content/en/docs/gke/monitoring.md

OWNERS: @Bobgy @joeliedtke @rmgogogo

Other guides:

content/en/docs/other-guides/kubeflow-on-multinode-cluster.md
content/en/docs/other-guides/freq-ask-questions.md
content/en/docs/other-guides/troubleshooting.md
content/en/docs/other-guides/istio-in-kubeflow.md
content/en/docs/other-guides/integrations/data-management.md
content/en/docs/other-guides/usage-reporting.md
content/en/docs/other-guides/job-scheduling.md

OWNERS: @8bitmp3 @RFMVasconcelos

Notebooks:

content/en/docs/notebooks/custom-notebook.md
content/en/docs/notebooks/troubleshoot.md
content/en/docs/notebooks/setup.md
content/en/docs/notebooks/submit-docker-image.md
content/en/docs/notebooks/submit-kubernetes.md
content/en/docs/notebooks/why-use-jupyter-notebook.md

No OWNERS file, should be created. Notebooks WG OWNERS: @thesuperzapper @StefanoFioravanzo @elikatsis @kimwnasptd

Reference:

content/en/docs/reference/mpijob/v1alpha2/mpi.md
content/en/docs/reference/pytorchjob/v1/pytorch.md
content/en/docs/reference/pytorchjob/v1beta2/pytorch.md
content/en/docs/reference/tfjob/v1/common.md
content/en/docs/reference/tfjob/v1/tensorflow.md
content/en/docs/reference/tfjob/v1beta2/common.md
content/en/docs/reference/tfjob/v1beta2/tensorflow.md

OWNERS: @andreyvelich @gaocegege @Jeffwan @johnugeorge @terrytangyuan

Bobgy commented 4 years ago

Hi @RFMVasconcelos, thank you for driving this. I've added OWNERS for multi-tenancy. https://github.com/kubeflow/website/blob/master/content/en/docs/components/multi-tenancy/OWNERS

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

rui-vas commented 3 years ago

Reopening as it is still relevant, we should finalize the cleaning :)

thesuperzapper commented 3 years ago

@RFMVasconcelos can you add this to the Docs Kanban: https://github.com/kubeflow/website/projects/2

rui-vas commented 3 years ago

Hey @thesuperzapper, sure. To be honest I think we're tackling a lot of the 69 remaining outdated files in the current changes. I'll include this so we can verify how many we have left and then close this Issue.

rui-vas commented 3 years ago

Is seems we're now at 50 outdated pages - list below:

content/en/docs/components/pipelines/caching.md
content/en/docs/components/pipelines/pipelines-quickstart.md
content/en/docs/components/pipelines/troubleshooting.md
content/en/docs/components/pipelines/sdk/output-viewer.md
content/en/docs/components/pipelines/sdk/enviroment_variables.md
content/en/docs/components/pipelines/sdk/best-practices.md
content/en/docs/components/pipelines/sdk/manipulate-resources.md
content/en/docs/components/pipelines/sdk/component-development.md
content/en/docs/components/pipelines/sdk/build-component.md
content/en/docs/components/pipelines/sdk/dsl-recursion.md
content/en/docs/components/pipelines/reference/component-spec.md
content/en/docs/components/training/mpi.md
content/en/docs/components/training/mxnet.md
content/en/docs/components/training/chainer.md
content/en/docs/components/training/pytorch.md
content/en/docs/components/training/tftraining.md
content/en/docs/components/serving/tritoninferenceserver.md
content/en/docs/components/serving/bentoml.md
content/en/docs/components/serving/tfserving_new.md
content/en/docs/components/serving/tfbatchpredict.md
content/en/docs/components/fairing/install-fairing.md
content/en/docs/components/fairing/fairing-overview.md
content/en/docs/components/fairing/configure-fairing.md
content/en/docs/components/fairing/tutorials/other-tutorials.md
content/en/docs/components/fairing/reference/sdk.md
content/en/docs/components/multi-tenancy/design.md
content/en/docs/components/istio/istio-in-kubeflow.md
content/en/docs/components/central-dash/registration-flow.md
content/en/docs/started/workstation/getting-started-minikf.md
content/en/docs/started/k8s/kfctl-existing-arrikto.md
content/en/docs/other-guides/integrations/data-management.md
content/en/docs/other-guides/troubleshooting.md
content/en/docs/other-guides/kubeflow-on-multinode-cluster.md
content/en/docs/other-guides/usage-reporting.md
content/en/docs/reference/pytorchjob/v1beta2/pytorch.md
content/en/docs/reference/pytorchjob/v1/pytorch.md
content/en/docs/reference/mpijob/v1alpha2/mpi.md
content/en/docs/reference/tfjob/v1beta2/common.md
content/en/docs/reference/tfjob/v1beta2/tensorflow.md
content/en/docs/reference/tfjob/v1/common.md
content/en/docs/reference/tfjob/v1/tensorflow.md
content/en/docs/gke/pipelines/enable-gpu-and-tpu.md
content/en/docs/gke/pipelines/preemptible.md
content/en/docs/gke/gcp-e2e.md
content/en/docs/gke/anthos.md
content/en/docs/gke/monitoring.md
content/en/docs/gke/cloud-filestore.md
content/en/docs/gke/troubleshooting-gke.md
content/en/docs/gke/deploy/monitor-iap-setup.md
content/en/docs/gke/customizing-gke.md
rui-vas commented 3 years ago

cc @kubeflow/wg-training-leads cc @kubeflow/wg-serving-leads cc @google-admin

thesuperzapper commented 3 years ago

@RFMVasconcelos do we have an updated list of which are still marked "out of date", as this looks bad

rui-vas commented 3 years ago

@thesuperzapper we are now at 38 files! The list now is:

content/en/docs/components/pipelines/caching.md
content/en/docs/components/pipelines/troubleshooting.md
content/en/docs/components/pipelines/sdk/output-viewer.md
content/en/docs/components/pipelines/sdk/enviroment_variables.md
content/en/docs/components/pipelines/sdk/best-practices.md
content/en/docs/components/pipelines/sdk/manipulate-resources.md
content/en/docs/components/pipelines/sdk/dsl-recursion.md
content/en/docs/components/pipelines/reference/component-spec.md
content/en/docs/components/central-dash/registration-flow.md
content/en/docs/distributions/gke/pipelines/enable-gpu-and-tpu.md
content/en/docs/distributions/gke/pipelines/preemptible.md
content/en/docs/distributions/gke/gcp-e2e.md
content/en/docs/distributions/gke/monitoring.md
content/en/docs/distributions/gke/cloud-filestore.md
content/en/docs/distributions/gke/troubleshooting-gke.md
content/en/docs/distributions/gke/deploy/monitor-iap-setup.md
content/en/docs/distributions/gke/customizing-gke.md
content/en/docs/other-guides/integrations/data-management.md
content/en/docs/other-guides/troubleshooting.md
content/en/docs/other-guides/kubeflow-on-multinode-cluster.md
content/en/docs/other-guides/usage-reporting.md
content/en/docs/external-add-ons/serving/tritoninferenceserver.md
content/en/docs/external-add-ons/serving/bentoml.md
content/en/docs/external-add-ons/serving/tfserving_new.md
content/en/docs/external-add-ons/serving/tfbatchpredict.md
content/en/docs/external-add-ons/fairing/install-fairing.md
content/en/docs/external-add-ons/fairing/fairing-overview.md
content/en/docs/external-add-ons/fairing/configure-fairing.md
content/en/docs/external-add-ons/fairing/tutorials/other-tutorials.md
content/en/docs/external-add-ons/fairing/reference/sdk.md
content/en/docs/external-add-ons/istio/istio-in-kubeflow.md
content/en/docs/reference/pytorchjob/v1beta2/pytorch.md
content/en/docs/reference/pytorchjob/v1/pytorch.md
content/en/docs/reference/mpijob/v1alpha2/mpi.md
content/en/docs/reference/tfjob/v1beta2/common.md
content/en/docs/reference/tfjob/v1beta2/tensorflow.md
content/en/docs/reference/tfjob/v1/common.md
content/en/docs/reference/tfjob/v1/tensorflow.md
rui-vas commented 3 years ago

@thesuperzapper you can track this list with the command: grep -lr 'This guide contains outdated information pertaining to Kubeflow 1.0.' content/en/docs reply: list

grep -lr 'This guide contains outdated information pertaining to Kubeflow 1.0.' content/en/docs | wc -l reply: 38

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

thesuperzapper commented 3 years ago

There are still many pages under "components" which have "outdated" headers, we should clean these up.

stale[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.