Swift 5.9 Release Process
This post describes the release process, and estimated schedule for Swift 5.9.
Snapshots of Swift 5.9
Downloadable snapshots of the Swift 5.9 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.9 is released, the official final builds will also be posted in addition to the snapshots.
Getting Changes into Swift 5.9
On March 20, 2023 the
release/5.9 branch will be cut in the swift repository and related project repositories. This will contain the changes that will be released in Swift 5.9. After the branch is cut, changes can be landed on the branch via pull request if they meet the criteria for the release.
Philosophy on Taking Changes into Swift 5.9
- All language and API changes for Swift 5.9 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.9 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 increasingly restrictive.
The following repositories will have a
release/5.9 branch to track
sources as part of Swift 5.9 release:
The llvm-project and swift-experimental-string-processing will have a corresponding swift/release/5.9 branch.
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.9 release as the release converges.
- Ben Cohen (@Ben_Cohen, GitHub: airspeedswift) is the overall release manager for Swift 5.9.
- Doug Gregor (@Douglas_Gregor, GitHub: DougGregor) is the release manager for the Swift Compiler.
- Ravi Kandhadai Madhavan (@ravikandhadai, GitHub: ravimad) is the release manager for llvm-project.
- Fred Riss (GitHub: fredriss) is the release manager for LLDB in llvm-project.
- Steve Canon (@scanon, GitHub: stephentyrone) is the release manager for the Swift Standard Library.
- Tony Parker (@Tony_Parker, GitHub: parkera) is the release manager for swift-corelibs-foundation.
- Rokhini Pabhu (@rokhinip, GitHub: Rokhini Prabhu) is the release manager for swift-corelibs-libdispatch.
- Brian Croom (GitHub: briancroom) is the release manager for swift-corelibs-xctest.
- Tom Doron (@tomerd, GitHub: Tom Doron) is the release manager for swift-package-manager.
- Daniel Dunbar (@ddunbar, GitHub: ddunbar) is the release manager for swift-llbuild and swift-tools-support-core.
- Ben Cohen (@Ben_Cohen, GitHub: airspeedswift) is the release manager for sourcekit-lsp, indexstore-db, swift-syntax, and swift-stress-tester.
- Franklin Schrans (@franklin, GitHub: franklinsch) is the release manager for swift-docc, swift-lmdb, swift-docc-render, swift-docc-render-artifact, swift-docc-symbolkit.
- Tony Allevato (@allevato, GitHub: allevato) is the release manager for swift-format.
Platform Release Managers
- Nicole Jacque (@Nicole_Jacque, GitHub: najacque) is the release manager for the Darwin platform.
- Tom Doron (@tomerd, GitHub: Tom Doron) is the release manager for Linux platforms.
- Saleem Abdulrasool (@compnerd, GitHub: compnerd) is the release manager for the Windows platform.
- Mishal Shah (@mishal_shah, GitHub: shahmishal) will be the release coordinator responsible for production of nightly and release snapshots and coordinating sign-off on repositories and platforms for the release.
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 (
release/5.9 ) after it has been cut, it must include the following information:
- 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.
- Issue: The GitHub Issue link if the change fixes/implements an issue/enhancement
- 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 useful.
All changes going on the
release/5.9 branch must go through pull requests that are accepted by the corresponding release manager.