Thanks Mishal! For all of the contributors to swift-corelibs: if you have a change which you think is appropriate for inclusion into Swift 3.1, let’s follow this process:
1. Get a PR up for master to merge your change 2. Once accepted, get a PR up to cherry pick the change to the swift-3.1 branch. We can have a discussion there about if it’s appropriate for swift 3.1, or we can chat about it on the mailing list first if you like. For Swift 3.1 changes, let’s focus on: * Regressions from Swift 3.0 * Critical work for server side Swift New work for unimplemented API can continue on master for the next Swift release. Thanks! - Tony > On Jan 17, 2017, at 2:33 PM, mishal_shah via swift-corelibs-dev > <swift-corelibs-dev@swift.org> wrote: > > I just merged master into swift-3.1-branch for following projects. > > https://github.com/apple/swift <https://github.com/apple/swift> > https://github.com/apple/swift-lldb <https://github.com/apple/swift-lldb> > https://github.com/apple/swift-corelibs-foundation > <https://github.com/apple/swift-corelibs-foundation> > https://github.com/apple/swift-corelibs-libdispatch > <https://github.com/apple/swift-corelibs-libdispatch> > https://github.com/apple/swift-corelibs-xctest > <https://github.com/apple/swift-corelibs-xctest> > https://github.com/apple/swift-integration-tests > <https://github.com/apple/swift-integration-tests> > https://github.com/apple/swift-xcode-playground-support > <https://github.com/apple/swift-xcode-playground-support> > https://github.com/apple/swift-package-manager > <https://github.com/apple/swift-package-manager> > https://github.com/apple/swift-llbuild > <https://github.com/apple/swift-llbuild> > > Thanks, > Mishal Shah >> On Jan 13, 2017, at 6:49 AM, Nicole Jacque via swift-build-dev >> <swift-build-...@swift.org <mailto:swift-build-...@swift.org>> wrote: >> >> Hello Swift Developers- >> >> As outlined in Ted’s Swift 3.1 Release Process blog post, for the past >> month, we’ve been periodically merging master to the swift-3.1-branch >> branch. We will be doing one final merge of master to the swift-3.1-branch >> on January 17 at noon (Pacific). Note that we’ve pushed this back a day due >> to the MLK Jr. Day holiday. Any changes landed after that time will >> require approval via a pull request against the swift-3.1-branch branch in >> order to include them in the Swift 3.1 release. After this final merge, >> development on master will be targeted for Swift 4. >> >> Snapshots of the swift-3.1-branch will be made available on the downloads >> page (https://swift.org/download/ <https://swift.org/download/>). Snapshots >> will be made available daily, if all package generation CI tests are passing. >> _______________________________________________ >> swift-build-dev mailing list >> swift-build-...@swift.org <mailto:swift-build-...@swift.org> >> https://lists.swift.org/mailman/listinfo/swift-build-dev > > _______________________________________________ > swift-corelibs-dev mailing list > swift-corelibs-dev@swift.org > https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
_______________________________________________ swift-corelibs-dev mailing list swift-corelibs-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
