Skip to content

Commit 1849e95

Browse files
authored
Release Roadmap for 2017.
1 parent 9030845 commit 1849e95

File tree

1 file changed

+34
-0
lines changed

1 file changed

+34
-0
lines changed

README.md

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,8 @@
88
🎉 [Getting Started](#getting-started)
99
⚠️ [Still using Swift 2.x?][]
1010

11+
12+
🚄 [Release Roadmap](#release-roadmap)
1113
## What is ReactiveSwift?
1214
__ReactiveSwift__ offers composable, declarative and flexible primitives that are built around the grand concept of ___streams of values over time___. These primitives can be used to uniformly represent common Cocoa and generic programming patterns that are fundamentally an act of observation, e.g.:
1315

@@ -332,6 +334,38 @@ We also provide a great Playground, so you can get used to ReactiveCocoa's opera
332334
## Have a question?
333335
If you need any help, please visit our [GitHub issues][] or [Stack Overflow][]. Feel free to file an issue if you do not manage to find any solution from the archives.
334336

337+
## Release Roadmap
338+
**Current Stable Release:**<br />[![GitHub release](https://img.shields.io/github/release/ReactiveCocoa/ReactiveSwift.svg)](https://github.com/ReactiveCocoa/ReactiveSwift/releases)
339+
340+
### In Development: ReactiveSwift 1.0
341+
It targets Swift 3.0.x. The tentative schedule of a Gold Master release is January 2017.
342+
343+
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.
344+
345+
A point release is expected with performance optimizations.
346+
347+
### Plan of Record
348+
#### ReactiveSwift 2.0
349+
It targets Swift 3.1.x. The estimated schedule is Spring 2017.
350+
351+
The release contains breaking changes. But they are not expected to affect the general mass of users, but only a few specific use cases.
352+
353+
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**.
354+
355+
ReactiveSwift 2.0 may include other proposed breaking changes.
356+
357+
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.
358+
359+
#### ReactiveSwift 3.0
360+
It targets Swift 4.0.x. The estimated schedule is late 2017.
361+
362+
The release may contain breaking changes, depending on what features are being delivered by Swift 4.0.
363+
364+
ReactiveSwift 3.0 would focus on two main goals:
365+
366+
1. Swift 4.0 Resilience
367+
2. Adapt to new features introduced in Swift 4.0 Phase 2.
368+
335369
[ReactiveCocoa]: https://github.com/ReactiveCocoa/ReactiveCocoa/#readme
336370
[Actions]: Documentation/FrameworkOverview.md#actions
337371
[Basic Operators]: Documentation/BasicOperators.md

0 commit comments

Comments
 (0)