[Release] Kubeflow Pipelines 1.2 umbrella tracker

[Bobgy]

/assign @Bobgy @Ark-kun
This should temporarily resolve issues like #4409.

TODOs:

• p0 fix master branch post submit test failure https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/kubeflow-pipeline-postsubmit-integration-test/1320555010165051392

[Bobgy]

We should probably finish #4540 first

[Bobgy]

Because we haven't been able to release a minor version for a while, this is our next priority

[Bobgy]

/cc @Ark-kun
The top blocker is fixing master branch postsubmit tests.

[Bobgy]

The most important next step can be releasing a 1.1.0-alpha.1 to allow dogfooding.

[Bobgy]

I'm going to release a 1.1.0-alpha.1 for preview, some non-core sample tests are failing in postsubmit including container builder. I'll ignore them for this release.

[Bobgy]

Auto generated changelog has a problem:
https:/kubeflow/pipelines/blob/7d36f48482d93f331664a851842276b733f1686a/CHANGELOG.md#110-alpha1-2020-11-02

It shows all changes from 0.5.1 to 1.1.0-alpha.1, because 1.0.0 was released on release-1.0 branch.

[Bobgy]

1.1.0-alpha.1 is released, feedback welcomed if there are any problems: https:/kubeflow/pipelines/releases/tag/1.1.0-alpha.1

[Bobgy]

/cc @rui5i
We need to upgrade MLMD to 0.25.1

Reference: google/ml-metadata#74 (comment)

[Bobgy]

And we need to wait for a resolution of #4847

[Bobgy]

@rui5i Handling #4855 properly is still tricky.
I'll write about what we need to do here.

/cc @chensun

[Bobgy]

EDIT: ignore the below, kfp SDK release is now separate, so releasing other stuff doesn't need to be blocked on it.

1. Merge chore(sdk): bump sdk's dependency on kfp-server-api #4855 (I've updated dependency to 'kfp-server-api>=1.1.1b1, <2.0.0', so the pre-released kfp-server-api 1.1.1b1 can be properly installed via pip)
2. Release 1.1.2-rc.1 as usual
3. During 1.1.2 release
   1. Run ./hack/release-imp.sh instead of ./hack/release.sh during release, the imp script add all changes to the local repo, so it's still possible editing the release commit before pushing it.
   2. Release kfp-server-api 1.1.2 in pypi directly from the local folder
   3. Update

      pipelines/sdk/python/setup.py

      Line 34 in 982b506

      'kfp-server-api>=0.2.5, <2.0.0',

      to >=1.1.2
   4. Commit the release commit and push to master
   5. Continue normal release process

[Bobgy]

/cc @chensun @Ark-kun
what do you think about above process for releasing change #4855?

Maybe, going forward, we should always release kfp-server-api package first in the release process, so kfp package can update its dependencies during release.

[chensun]

1. Merge chore(sdk): bump sdk's dependency on kfp-server-api #4855 (I've updated dependency to 'kfp-server-api>=1.1.1b1, <2.0.0'

The offending PR only exists in master, thus not available in 1.1.1b1, right? In that case, isn't 1.1.1b1 the same as 0.2.5?
If that's the case, then we can release 1.1.2-rc1 as usual without waiting for #4855, given we're not releasing kfp package 1.1.2-rc1. Instead, we are releasing kfp 1.1.2 from master. And only this step is blocked by the setup.py change with kfp-server-api>=1.1.2-rc1 (or >1.1.1).

Maybe, going forward, we should always release kfp-server-api package first in the release process, so kfp package can update its dependencies during release.

Agree.

[Bobgy]

@chensun the offending PR was released in 1.1.1b1 already, but yes, you are right this only blocks kfp release, we can skip this problem for backend release.

[chensun]

@chensun the offending PR was released in 1.1.1b1 already, but yes, you are right this only blocks kfp release, we can skip this problem for backend release.

I see. Then we can merge #4855 as-is.

[Bobgy]

Release blocker: #4903

[Bobgy]

All done