Update our track strategy for the Kubeflow 1.9 release

[ca-scribner]

Context

In recent releases we have not promoted charms to latest/stable in the charm repositories, leading to confusion. This was in part because we discussed removing the latest track entirely from our charms, instead opting to update our default track to whatever is the most recent release (say 1.8).

We should define what we want (do we use latest at all? do we promote to latest/stable? etc) before the 1.9 release

What needs to get done

1. define and document our track strategy for charms

Definition of Done

1. track strategy for charms is defined and documented

[syncronize-issues-to-jira]

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5652.

This message was autogenerated

[orfeas-k]

Discussed in https://docs.google.com/document/d/1WYWf8BEbB_nPasVwBWaDhhmnu461hZdFNVSAA4an1-s/edit#heading=h.lfxtpxci0bkl

[orfeas-k]

Context

(a) What should we do with the latest/stable track? Where should it point to and if it should even exist?
(b) What would be the default track when deploying a charm?

Options

For (a), options are:

1. latest/stable → /stable - should we do this just for the bundle or for charms as well?
2. get rid of latest/stable - means we will have to update the default one
3. latest/stable → latest/edge
   For (b), options are:
4. <version>/stable is default
5. keep latest/stable as default
6. latest/edge is default

Conclusions:

1. Hide latest/stable in both bundle and charms
2. Change the default track to be a version
3. Expect latest/candidate and latest/beta only for testing (SolQA), but we do NOT expect anyone to use it in our docs
4. Let’s deprecate/remove/hide the 1.7 (and previous unmaintained) tracks for both bundle and corresponding charms

[NohaIhab]

thanks for the summary from tech topics @orfeas-k

I've requested to change the default tracks for the bundle and charms. They are now in effect. The default tracks for the kubeflow bundle and charms have been changed to those corresponding to 1.9.

[NohaIhab]

Pushed changes

Based on the conclusion with the team, I pushed the following changes.

1. All the latest/stable channels for kubeflow bundle and charms are hidden
2. The default tracks for kubeflow bundle and charms are now set to the tracks corresponding to 1.9.
3. Closed all the channels corresponding to kubeflow bundle < 1.7.
   • Note: I kept the 1.7 tracks as it is still being used by some customers
4. Added a task in the Release handbook to change the default tracks to the new release version with every release.

In response to:

Expect latest/candidate and latest/beta only for testing (SolQA), but we do NOT expect anyone to use it in our docs

I checked all of our docs, none of them are pointing to latest/beta or latest/candidate.

[NohaIhab]

I have filed #1126 to track closing the 1.7 channels once we check it is not being used, this issue can be closed now.