Preparing v1.1.1-incubating release

[bobbai00]

Task Summary

This task is used to track the TODOs for v1.1.1-incubating release.

For v1.1.0-incubating, see #4080

Task Type

• Refactor / Cleanup
• DevOps / Deployment / CI
• Testing / QA
• Documentation
• Performance
• Other

[Yicong-Huang]

we need to decide when to cut branch

[bobbai00]

we need to decide when to cut branch

Shouldn't we checkout from branch release/v1.1.0-incubating and then backport the PRs to that?

[Yicong-Huang]

That is what I meant of "a branch cut": checkout from a base to a new branch.

The question is do we want to use v1.1.0-incubating as the base, or use main as the base for the new release. I think we have the freedom to choose, also it depends on if those two releases have breaking changes.

[bobbai00]

@Yicong-Huang Got it! Thanks for the clarification.

I support the idea of branching out from v1.1.0-incubating, and making NO breaking changes between 1.1.1 and 1.1.0. I already put some bug fixes I want to include in 1.1.1 as sub-issues.

[Yicong-Huang]

A bigger problem is, do we want to release maintenance versions (i.e., 1.1.1), or we should bump minor version (I.e., 1.2.0)?

[Yicong-Huang]

Let me send out a discussion about this.