Istio Release 1.6

Timeline

All dates are tentative

• Branch Cut/Feature Freeze: April 24th, 2020. Branch cut from 7ea912bb28.
• Community Test Day #1: April 29, 2020
• Community Test Day #2: May 11, 2020
• Code Freeze: May 13, 2020
• Release Date: May 21, 2020

Release Managers

• Iris: irisdingbj
• Brian Avery: brian-avery
• Jacob Delgado: jacob-delgado

Release Notes Draft

1.6 Release Notes Draft: https://docs.google.com/document/d/1smIYqaRA4MXhmRKYLgwr74rxPgOk1UP9ppiFHa6Q4d0/edit Upgrade Notes Draft: https://docs.google.com/document/d/1F4Yc3AnwRB_1n87vz2IR_jnQp4QB6dTpeBt6pCEBrnc/edit

For any new, user facing changes targeting Istio 1.6, please add a note below. Examples can be found from the previous release: https://istio.io/news/2019/announcing-1.3/#release-notes. Please format entries following the Release Note Schema.

How do I get my changes into the release?

On TODO, the release-1.6 branch will be created, based on master. Any changes on master before this date will be included in the release. Any changes after will have to be cherry picked.

To get a PR merged into the release branch, it must first be merged into the master branch. PRs can automatically be cherrypicked by typing by adding the cherrypick/release-1.6 label to the PR.

A PR on the release branch will only be approved if:

• The change is already on master.
  • exception: if a change only applies to the release branch, and should not go to master, a change can be submitted directly to the release branch, but please note this in the PR description.
• The change is a bug fix, documentation enhancement, or testing enhancement.
  • Changes that are risky may require a feature flag, especially after the 1.6.0 release.
  • Any change not meeting the above, such as a new feature or API, may require TOC approval.

Note: on the istio.io repo, changes should go directly to master until after the 1.6.0 launch. The changes will appear on preliminary istio.io.