Bump pipeline version to 0.2.5 in v1.0-branch

[Jeffwan]

Pipeline version in Kubeflow v1.0 is 0.2.0 which has been released for 2 months.
I suggest to bump the version to 0.2.5 in v1.0-branch as it contains some performance critical improvements.

Examples:
kubeflow/pipelines#3165

/cc @richardsliu @Bobgy @Ark-kun

[issue-label-bot]

Issue-Label Bot is automatically applying the labels:

Label	Probability
feature	0.66

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

[Bobgy]

Yep, I think we should do this. I'd like to know others' opinions too.

Related issues include

• KF 1.0: KFP UI produces ugly results when not on GKE kubeflow#4829
• ServiceException: 409 Bucket ml-pipeline-playground already exists pipelines#3069 (comment)

[Jeffwan]

Hi @Bobgy, Not sure any compatibility concerns to use 0.2.5 in v1.0-branch? I think the plan could be use 0.2.5 is master, run some manual tests and if cherry-pick back to v1.0-branch?

[Bobgy]

I don't think there are any compatibility issues, KFP has been backward compatible from 0.2.0 to 0.2.5

[Jeffwan]

@Bobgy Cool, thanks for the confirmation. Kindly ping @Ark-kun @rmgogogo for their feedbacks

[Bobgy]

@Ark-kun @rmgogogo pinging again

[elikatsis]

This (important) issue is also resolved in KFP>0.2.0 (included in release 0.2.1): kubeflow/pipelines#2764

[Bobgy]

I'd like to send a PR to update KFP to 0.3.0 instead, because we'd make sure kfp is not broken due to kubeflow/kfctl#131.

KFP 0.3.0 included the fix: kubeflow/pipelines#3305

[Bobgy]

I didn't see this issue is about v1.0-branch. Actually I only intended to upgrade to 0.3.0 in master branch, because it was not as heavily tested as 0.2.5. I'd still recommend 0.2.5 for v1.0-branch.

[Jeffwan]

We need to discuss whether we like to cut v1.1-branch. If it's coming soon, it's fine to leave v1.0-branch with existing version