Istio Release 1.4

Istio Release 1.4

Timeline

• October 16 release-1.4 branch cut
• October 18 Istio 1.4.0-alpha.0 Released
• October 22 First Community Testing Day
• October 23 Istio 1.4.0-beta.0 Released
• October 29 Istio 1.4.0-beta.1 Released
• October 29 Second Community Testing Day
• November 5th Istio 1.4.0-beta.2 Released
• November 8th Istio 1.4.0-beta.3 Released
• November 11th Istio 1.4.0-beta.4 Released
• November 13th Istio 1.4.0-beta.5 (release candidate) Released
• November 14 Istio 1.4.0 Released
• December 5th Istio 1.4.1 Released
• December 10th Istio 1.4.2 Released
• Expected January 8th Istio 1.4.3 Released

Release Managers

• @ericvn
• @jwendell
• @howardjohn

Useful Links

• Release Notes

How do I get my changes into the release?

On 10/16, the release-1.4 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 /cherrypick release-1.4 in a comment on the PR, or adding the cherrypick/release-1.4 label to the PR (note - the label must be added before the PR is merged, but the comment can be done at any time).

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.4.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 now go to release-1.4. Changes to master` will appear on preliminary istio.io in preparation for the next release.