Remove mention of all past versions

[RichieEscarez]

Going forward, knative.dev should only mention breaking or important changes from one previous version (v.latest -1).

Todo:

• All references to any other version should be removed
• If necessary, revise all content to consider only one version prior (otherwise remove mention of a version altogether)
• If we must mention something, consider adding it to a migration guide or known issues page

We should assume that users understand that if you view the latest release (ie. v0.10), that all references imply that version (ie. Install Serving/Eventing, etc.).

If there is a circumstance that requires you to define the "current" version, you can insert a dynamic variable ({{% version %}} shortcode) that gets populated at build time with the version number of whatever the latest release is:

Insert {{% version %}} where you want the version number to show. See examples.

Example:
The line about "Knative 0.3x" should be removed and revised:
https://knative.dev/docs/install/knative-custom-install/#installing-knative

[abrennan89]

Is there a way to also filter search results by version or prevent these from showing up older versions of docs mixed in with the latest docs? It makes the search a little confusing to use IMHO because you have to check the link to make sure the docs aren't from an older version every time.

[RichieEscarez]

Yeah, I feel the same about our search too. I've had that on my to-do list since the site launch but have not been able to get to it. There is an open issue about this here: knative/website#46

[abrennan89]

/assign abrennan89

[abrennan89]

Version mentions from review:

• Installing Knative > MicroK8s > Enable Knative (mentions Serving & Eventing 0.7.1)
  • Also has a note about updating versions in the doc. We should remove the note if we're not going to track / commit to tracking this for each version.
• Installing Knative > Checking your install version (mentions pre-0.4.0)
• Serving component > Configuring the autoscaler (mentions v0.2 and links to v0.3 blog post)
• Serving component > Debugging issues w/ your application > Check ingress status (mentions 0.3)
• Serving component > Setting up a custom domain > deploy an application (example/code mentions multiple versions in comments)
• Serving component > Configuring HTTPS with cert-manager and Google Cloud DNS > Before you begin (mentions 0.6.0)
• Serving component > Enabling autoTLS certs > Before you begin (mentions Serving v0.6.0)
• Eventing component > Event brokers and triggers (mentions 0.5.0)
• Eventing component > Event registry (mentions 0.6.0)
• Eventing component > Code samples > Parallel (mentions Knative "Service" 0.8+)
• Eventing component > Debugging (mentions v0.8.0 Eventing)
• Installing Knative > Azure Kubernetes Service > Installing Knative (mentions 0.3.x)
• Installing Knative > IBM Cloud Private > Installing Knative (mentions 0.3.x)
• Installing Knative > On existing cluster > Installing Knative (mentions 0.3.x)

@RichieEscarez I think this should be all of them but lmk if there's any other instances that need to be removed.
I don't think there's anything that needs to be revised to one version prior except maybe the Parallel code sample, and I don't think anything here needs to be in a known issues/migration guide.

[abrennan89]

@RichieEscarez @samodell any idea what to do about the last three on this list? Do we need a migration guide?
I will double check this is all of them with fresh eyes tomorrow 🙂