-
Notifications
You must be signed in to change notification settings - Fork 227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Time for a new release? #70
Comments
Possibly a prerelease, but I’d like to avoid 0.6 final til Swift 2 lands. |
agreed a prerelease, up to you 👍 |
A release on CocoaPods with Swift 2 compatibility would also be much appreciated! 😄 |
@Thomvis I’ve invited you to the repo. PRs are appreciated for any non-trivial changes, but you’d be welcome to tag e.g. 0.6-beta1 at your leisure 😄 |
@robrix thanks so much! I've created a 0.6-beta.1 release. Let me know if you want to have anything changed. I don't think I can push this release to CocoaPods. @gfontenot perhaps? (You're listed as a maintainer https://cocoapods.org/pods/Result.) |
on it. Happy to add you as a maintainer in CP as well. Just let me know which address to send it to. |
👍 Thank you @Thomvis! I’m deeply indebted to each of the various contributors who’ve submitted PRs, added tags, reviewed code, filed issues, and otherwise helped out. |
@gfontenot sent you an email! |
Added you as a maintainer, but it looks like CocoaPods (0.37) is crashing while trying to validate the pod. Feel free to push if you can figure that out. |
I also encountered that crash when working on a different pod. Probably this issue? Do you host the podspec somewhere, or should I just grab it from the specs repo, update it and push it again? |
I just grabbed the JSON version from the specs repo and have been updating that. |
I was able to push a new version of the spec using the latest beta version of CocoaPods! See https://cocoapods.org/pods/Result |
quite a few changes were made since https://github.com/antitypical/Result/releases/tag/0.5 perhaps it's time to create a new releases...
The text was updated successfully, but these errors were encountered: