-
Notifications
You must be signed in to change notification settings - Fork 6
Swift 2.3 release #14
Comments
Hi, Sorry but our Swift 2.3 branch will stay a branch. We will support this branch for a moment, but our official release is for Swift 3.0. Regards |
As an external dependency, it's a good practice to provide official support in form of a release to your consumers. Think that maybe it is not easy to move to Swift3 right away for a really big app and having an stable 2.3 release in the meantime provides some piece of mind for your users :) |
Sorry but I'm not sure why our SDK that supports Swift 2.3, being a branch, is a problem for you ? You can easily select this branch via Cocoapod. We will support this branch until Swift 2.3 disappears. I know it's not that easy to migrate from Swift 2.2 to Swift 3.0 (we've been there ;)) but Swift 3.0 is our official release. Swift 2.3 is just here to make the transition easier. Regards |
I prefer to rely on fixed versions that are easy to track rather than branches than can be updated without us noticing. Seeing a commit ref change in the Podfile.lock after performing a merge does not raise the same kind of alarms as moving from x.y to x.y+1, it's much more straightforward to know what's going on |
Ok, we will see what we can't do for our next release. Regards |
Thank you, really appreciate it 👍 |
Hi,
I have noticed that 2.2.5 is Swift 2.2 and 2.3 is Swift 3.0, while 2.3 support is just a branch. Any chance to get an official release?
Thanks,
The text was updated successfully, but these errors were encountered: