We are pleased to announce the completion of the branch cut work for the upcoming Istio 1.20 release and the release of our first beta.
The release can be found on Github here . Please test and report any issues found. Beta.1 is expected in a week’s time.
We would also like to bring to your attention some information related to the release:
- No new feature requests will be accepted to the 1.20 branch. Any exceptions will require TOC approval.
- Bug fixes will be accepted to the 1.20 branch after being reviewed by the 1.20 release managers. To get changes into the 1.20 branch, they must be merged first to master then add the cherry-pick label for 1.20 to be automatically cherry-picked to the 1.20 release branch. If the automatic cherry -pick fails, you may have to manually cherry-pick the changes to the release-1.20 branch.
- Commits with no-risk of impacting stability during our tests will mostly be approved. Fixes for regressions will be considered with the highest priority. Any bug fix with a high risk of introducing regressions will be rejected.
- Examples of bad patterns to avoid for back porting changes from master:
- Master PR is submitted that implicitly relies on other PRs in master; someone unrelated to the PR (not familiar with the dependency) triggers a backport and it merges.
- Backports should have a mutual agreement between release managers, original PR submitter (if they are a maintainer), and original approvers.
- A submission/approval to master doesn’t mean that person thinks it’s safe to backport.
- PR marked as “Do not backport until X” in the description backported without X happening.
- Reviewer 1 leaves critical comment on master PR; Reviewer 2 approves and it merges; Backport is done immediately after, and code with critical comments is shipped.