Tf-operator: Cut release for tf-operator project

[Jeffwan]

Seems the latest tag for tf-operator is v0.5.3. There's a v1.0.0 pre-release.
Trying to discuss if the release procedure. Do you want to keep sync with kubeflow release? like v1.1.0 or it doesn't have to follow the pattern? (Currently, every 3 - 4 months, Kubeflow will have a major release.)

To better manage releases, there're two patterns

1. Cut branch, cut release against branch, bug fixes should come into master and cherry-pick to feature branch. (this will be similar to Kubernetes/kubernetes and kubeflow/manifest)
2. Don't use branch, alway cut release on master.

[Jeffwan]

I will help cut v1.0.0 and probably v1.0.x releases based on changes from last June to now.. #1161 will brings breaking changes (API, implementation and batch scheduler), we will cut v1.1.0 release later.

[issue-label-bot[bot]]

Issue-Label Bot is automatically applying the labels:

| Label | Probability |
| ------------- | ------------- |
| feature | 0.68 |

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

[stale[bot]]

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.

[Jeffwan]

/reopen

[k8s-ci-robot]

@Jeffwan: Reopened this issue.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[stale[bot]]

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.