This post describes the release process, and estimated schedule for Swift 5.6.
Downloadable snapshots of the Swift 5.6 release branch will be posted regularly as part of continuous integration testing. As support is available, snapshot downloads will be added for newly supported platforms.
Once Swift 5.6 is released, the official final builds will also be posted in addition to the snapshots.
On December 7, 2021 the
release/5.6 branch will be cut in the swift repository and related project repositories. This will contain the changes that will be released in Swift 5.6. After the branch is cut, changes can be landed on the branch via pull request if they meet the criteria for the release.
All language and API changes for Swift 5.6 will go through the Swift
Evolution process. Evolution
proposals should aim to be completed by the branch date in order to
increase their chances of impacting the Swift 5.6 release. Exceptions
will be considered on a case-by-case basis, particularly if they tie
in with the core goal of the release.
Other changes (e.g., bug fixes, diagnostic improvements, SourceKit interface
improvements) will be accepted based on their risk and impact.
Low-risk test tweaks will also be accepted late into the release branch if
it aids in the qualification of the release.
As the release converges, the criteria for accepted changes will become
The following repositories will have a
release/5.6 branch to track
sources as part of Swift 5.6 release:
The llvm-project will have a corresponding
The overall management of the release will be overseen by the following
individuals, who will announce when stricter control of change goes into
effect for the Swift 5.6 release as the release converges.
Ben Cohen is the overall release manager for Swift 5.6.
Doug Gregor is the release manager for the Swift Compiler
Kyle Macomber is the release manager for the
Swift Standard Library.
Nicole Jacque is the release manager for the Darwin platform.
Tom Doron is the release manager for Linux platforms.
Saleem Abdulrasool is the release manager for the Windows platform.
In order for a pull request to be considered for inclusion in the release
release/5.6) after it has been cut, it must include the following
Explanation: A description of the issue being fixed or enhancement being
made. This can be brief, but it should be clear.
Scope: An assessment of the impact/importance of the change. For
example, is the change a source-breaking language change, etc.
SR Issue: The SR if the change fixes/implements an issue/enhancement on
Risk: What is the (specific) risk to the release for taking this change?
Testing: What specific testing has been done or needs to be done to
further validate any impact of this change?
Reviewer: One or more code owners
for the impacted components should review the change. Technical review can
be delegated by a code owner or otherwise requested as deemed appropriate or
All changes going on the
release/5.6 branch must go through pull requests that are
accepted by the corresponding release manager.