You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to have all the recent changes released in a new Cocoapods version / Github release since the current release was the first public one in March of 2015. Pointing to a specific commit works but isn't the most ideal scenario and doesn't reflect how much has changed in the repo and the scope of those changes with semantic versioning. It seems like there might be a great opportunity to create a new release after #114 is merged.
The text was updated successfully, but these errors were encountered:
Thanks for bringing this up, @bcapps. Internally we are looking at tagging a 1.0.0 release once we're confident that #102 (close button missing) is totally resolved.
Ideally such a major release would include a fix for #109 and Carthage support (#61)—our team is getting close to fully understanding what's required for us to support Carthage properly. But we probably won't consider either of these blocking for a 1.0 release.
It would be nice to have all the recent changes released in a new Cocoapods version / Github release since the current release was the first public one in March of 2015. Pointing to a specific commit works but isn't the most ideal scenario and doesn't reflect how much has changed in the repo and the scope of those changes with semantic versioning. It seems like there might be a great opportunity to create a new release after #114 is merged.
The text was updated successfully, but these errors were encountered: