Swift 5.2 Release Process

This post describes the goals, release process, and estimated schedule for Swift 5.2.

Motivation and Goals

Swift 5.2 is a release meant to include significant quality and performance enhancements.

Snapshots of Swift 5.2

Downloadable snapshots of the Swift 5.2 release branch will be posted regularly as part of continuous integration testing.

Once Swift 5.2 is released, the official final builds will also be posted in addition to the snapshots.

Getting Changes into Swift 5.2

On December 9, 2019 the swift-5.2-branch branch will be cut, and this will contain the changes that will be released in Swift 5.2. After the branch is cut, changes can be landed on the branch via pull request if the meet the criteria for the release.

Some notable exceptions to this plan are indicated in the table below. Each will merge from master into swift-5.2-branch daily. The final cutoff date for changes to each exception will extend beyond November 5 and will be announced later.

Project Cutoff date
indexstore-db January 7, 2020
sourcekit-lsp January 7, 2020
swift-llbuild January 7, 2020
swift-package-manager January 7, 2020

Philosophy on Taking Changes into Swift 5.2

Impacted Repositories

The following repositories will have a swift-5.2-branch branch to track sources as part of Swift 5.2 release:

Release Managers

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.2 release as the release converges:

Please feel free to post on the development forum or contact Ted Kremenek directly concerning any questions about the release management process.

Pull Requests for Release Branch

In order for a pull request to be considered for inclusion in the release branch (swift-5.2-branch) after it has been cut, it must include the following information:

All change going on the swift-5.2-branch must go through pull requests that are accepted by the corresponding release manager.