Conversation
Those should be recovered on the future commits or the branch that supports Swift 3.0.
| dist: trusty | ||
| language: generic | ||
| install: | ||
| - eval "$(curl -sL https://gist.githubusercontent.com/kylef/5c0475ff02b7c7671d2a/raw/02090c7ede5a637b76e6df1710e83cd0bbe7dcdf/swiftenv-install.sh)" |
There was a problem hiding this comment.
Why did this job need to be removed?
There was a problem hiding this comment.
I tried to update to a recent snapshot as of https://github.com/jpsim/Commandant/tree/jp-05-31-snapshot, but that requires breaking changes and I gave it up. So this should be my fault at that time.
|
Oh, I remembered that Result 2.1.0 breaks the builds for DEVELOPMENT-SNAPSHOT-2016-03-24-a.
But updating to DEVELOPMENT-SNAPSHOT-2016-05-31-a requires a large number of |
|
Should we support Swift 2.3 and Swift 3 (DEVELOPMENT-SNAPSHOT-2016-05-31-a) simultaneously as Result does on its |
|
I think Commandant can stick to supporting just 1 version of Swift. |
|
Updating |
|
✨ Just waiting on Travis now. 👍 |
No description provided.