-
Notifications
You must be signed in to change notification settings - Fork 8.2k
Istio Release 1.11
📣 Release has been pushed back 1 week from Aug 3rd to Aug 10th 📣
- Branch Cut/Feature Freeze:
July 9th, 2021July 14th, 2021 at 241a9f7e21417087972076918959cdb9cf17cd1f - Code Freeze: Aug 3rd, 2021
- Release Date:
Aug 10th, 2021Aug 12th, 2021
- 1.11.1: Aug 24th, 2021 - CVE release
- 1.11.2: Sep 2nd, 2021 - Normal 3-week cadence release
- 1.11.3: Sep 23rd, 2021 - Normal 3-week cadence release
- 1.11.4: Oct 15th, 2021 - Normal 3-week cadence release
- 1.11.5: Dec 3rd, 2021 - Normal release
- 1.11.6: Feb 3rd, 2021 - Normal release
- 1.11.7: Feb 22nd, 2021 - CVE release
- 1.11.8: Mar 9th, 2021 - CVE, last release
- Jonh Wendell (Red Hat): @jwendell
- Ryan King (Solo.io): @ryantking
- Steve Zhang (Intel): @zhlsunshine
- Release Notes Draft:
- Upgrade Notes Draft:
For any new, user facing changes targeting Istio 1.11, 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.
On July 12th, 2021, the release-1.11 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.11 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.
- exception: if a change only applies to the release branch, and should not go to
- The change is a bug fix, documentation enhancement, or testing enhancement.
- Changes that are risky may require a feature flag, especially after the 1.11.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.11.0 launch. The changes will appear on preliminary istio.io.
Visit istio.io to learn how to use Istio.
- Preparing for Development Mac
- Preparing for Development Linux
- Troubleshooting Development Environment
- Repository Map
- GitHub Workflow
- Github Gmail Filters
- Using the Code Base
- Developing with Minikube
- Remote Debugging
- Verify your Docker Environment
- Istio Test Framework
- Working with Prow
- Test Grid
- Code Coverage FAQ
- Writing Good Integration Tests
- Test Flakes
- Release Manager Expectations
- Preparing Istio Releases
- Release Automation Tool Information
- Release Process Template Checklist
- 1.5 Release Information
- 1.6 Release Information
- 1.7 Release Information
- 1.8 Release Information
- 1.9 Release Information
- 1.10 Release Information
- 1.11 Release Information
- 1.12 Release Information
- 1.13 Release Information
- 1.14 Release Information
- 1.15 Release Information
- 1.16 Release Information
- 1.17 Release Information
- 1.18 Release Information
- 1.19 Release Information
- 1.20 Release Information
- 1.21 Release Information
- 1.22 Release Information
- 1.23 Release Information
- 1.24 Release Information
- 1.25 Release Information
- 1.26 Release Information
- 1.27 Release Information
- 1.28 Release Information
- 1.29 Release Information