<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi everyone,<br class=""><br class="">I am very pleased to announce the release of Swift 2.2! This is the first release of Swift since Swift became an open source project. Swift 2.2 began it’s convergence in mid-January when it branched from master, and since then is had taken curated changes (bug fixes and some language changes) that were aligned with the goals of the release.<br class=""><br class="">We have an official release announcement on the <a href="http://Swift.org" class="">Swift.org</a> blog:<br class=""><br class=""> https://swift.org/blog/swift-2-2-released/<br class=""><br class=""><br class="">Being a minor release, the purpose of Swift 2.2 was to be a transition point between Swift 2 and Swift 3. Swift 2.2 went through a release process that will be a prototype for future Swift releases. The release process was described here:<br class=""><br class=""> https://swift.org/blog/swift-2-2-release-process/<br class=""><br class=""><br class="">While Swift 2.2 contains support for Swift on Linux, support for that platform in Swift 2.2 should still be considered relatively new. The Package Manager is not included in this release, nor are the Swift Core Libraries.<br class=""><br class="">Qualification for Swift 2.2 was based on regression tests (run in continuous integration), users reporting issues with downloadable Swift 2.2 packages, and seeding of the Swift 2.2 compiler in Xcode 7.3 seeds. In the future I’d like to beef up our qualification processes around Linux, including more extensive testing of the compiler and LLDB. Any feedback from the community is welcome on how we can improve it.<br class=""><br class="">The swift-2.2-branch release branch will remain “open” under the same release manager process of Swift 2.2. The branch can take targeted fixes in the chance that we decide to release a Swift 2.2 dot release. This would largely be driven by feedback from users.<br class=""><br class="">The final tag in GitHub for the release (for the impacted repositories) is ‘swift-2.2-RELEASE’.<br class=""><br class="">Cheers,<br class="">Ted</body></html>