The 2017 Roadmap
It targets Swift 3.0.x. The tentative schedule of a Gold Master release is January 2017.
A Release Candidate would be released after an important bug fix and an API renaming PR are cleared, which should happen no later than Christmas 2016.
A point release is expected with performance optimizations.
It targets Swift 3.1.x. The estimated schedule is Spring 2017.
The release contains breaking changes. But they are not expected to affect the general mass of users, but only a few specific use cases.
The primary goal of ReactiveSwift 2.0 is to remove single-implementation protocols, e.g. SignalProtocol, SignalProducerProtocol, that serve as a workaround to concrete same-type requirements.
ReactiveSwift 2.0 may include other proposed breaking changes.
As resilience would be enforced in Swift 4.0, it is important for us to have a clean and steady API to start with. The expectation is to have the API cleanup and the reviewing to be concluded in ReactiveSwift 2.0, before we move on to ReactiveSwift 3.0 and Swift 4.0. Any contribution to help realising this goal is welcomed.
It targets Swift 4.0.x. The estimated schedule is late 2017.
The release may contain breaking changes, depending on what features are being delivered by Swift 4.0.
ReactiveSwift 3.0 would focus on two main goals:
- Swift 4.0 Resilience
- Adapt to new features introduced in Swift 4.0 Phase 2.