update release doc

[gabrielwen]

Adding instructions for joining release team and updating application version.

---

This change is 

[jlewi]

@gabrielwen Could you do a pass through the release doc please and update any sections that no longer make sense; there is a lot of outdated information.

I think it would be great to talk about the following

1. How to prepare individual applications for release

   • e.g. for TFJob and PYtorch; cut release branches for those applications
   • Update kubeflow/manifests master to use them

2. How to cut a release branch of kubeflow/manifests and prepare it for relesae

   • e.g. update the Kubeflow application resource version to the upcoming major.minor release

3. How to cut a kfctl release

   • e.g. cut the branch; update releases etc.

4. How to update the KFDef specs on the release branch

   * The repos section should be pinned to specific commits on the release branch
   

We can also delete a bunch of outdated references to ksonnet
e.g. update or delete all references to ksonnet; e.g. the section Updating ksonnet prototypes with docker image and the section "Updating the ksonnet configs for master"

[jlewi]

We should also add some steps about looking at the test grid to ensure tests are passing.

• It looks like one thing we need to document is that the tests on the release branch need to be updated to use the configs from the release branch.

[jlewi]

@gabrielwen Think we can wrap this up this week?

[gabrielwen]

Yes, we should be able to. I forgot what I was trying to add to, but will finish this up this week.

[gabrielwen]

@jlewi should be ready, could you take a look? thanks.

[jlewi]

@gabrielwen see my previous comment it looks like we are still missing a bunch of information.

Here's my meta comment. Can we try to define a clear process that would be easy for someone to follow?

Lets add a section about releasing all the individual components

In this section lets create a list of all the components that should be updated as part of each release

• TFJob
• PyTorch
• JupyterWebapp
• CentralDashboard
• Katib
• ProfileController
• NotebookController

The instructions should say something like the following

1. Create release branch for all of the above
2. Create a Kubernetes periodic prow job for the release branch
3. Update the prow_config.yaml on the release branch if necessary
   • i.e. kfctl v0.Y-branch should pull in v0.Y branch of kubeflow-manifests
4. Check that postsubmits on the branch are green
5. Build and publish docker images to gcr.io/kubeflow-images-public for all of the above
6. Update kustomize manifest on kubeflow/manifest to reference the above

Once all of the application manifests on kubeflow/master have been updated we are ready to cut a release branch

Once we cut the release branch of kubeflow/manifests lets list out all the steps that need to be performed

1. Create a periodic prow job
2. Update prow_config to use the v0.Y branch of kfctl
3. Update application version in all applications

[jlewi]

@gabrielwen let me know when this is ready for another look?

[gabrielwen]

working on this now.

[gabrielwen]

@jlewi updated, could you also take a look? I'll also take second pass tonight.

[jlewi]

This is great; thanks @gabrielwen

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jlewi

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jlewi]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment