Currently the deprecation roadmap is noted in the README as follows:
The deprecating plan is a 3 major versions removal. Which is as follows:
- Introduce new Predicate API, deprecation warning for old matcher APIs. (Nimble v7.x.x)
- Introduce warnings on migration-path features (.predicate, Predicate-constructors with similar arguments to old API). (Nimble v8.x.x)
- Remove old API. (Nimble v9.x.x)
I think we are not ready for v8 release yet but maintaining v7 release (at 7.x-branch) for 3 Swift versions (Swift 3, Swift 4 and Swift 4.2) and many Xcode versions (from Xcode 8 to Xcode 10.1) is so difficult and tedious.
So I propose releasing Nimble v8 just for bumping Swift version requirement to Swift 4.2 with no API changes since v7.3.2. That should fairly make the development easier.
As a result,
- Introduce warnings on migration-path features (.predicate, Predicate-constructors with similar arguments to old API). (Nimble v8.x.x)
will be Nimble v9.x.x and
- Remove old API. (Nimble v9.x.x)
will be Nimble v10.x.x.
@Quick/core How do you think?
Currently the deprecation roadmap is noted in the README as follows:
I think we are not ready for v8 release yet but maintaining v7 release (at
7.x-branch) for 3 Swift versions (Swift 3, Swift 4 and Swift 4.2) and many Xcode versions (from Xcode 8 to Xcode 10.1) is so difficult and tedious.So I propose releasing Nimble v8 just for bumping Swift version requirement to Swift 4.2 with no API changes since v7.3.2. That should fairly make the development easier.
As a result,
will be Nimble v9.x.x and
will be Nimble v10.x.x.
@Quick/core How do you think?