-
Notifications
You must be signed in to change notification settings - Fork 94
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
Specs update #6
Specs update #6
Conversation
@@ -106,7 +106,8 @@ When you are preparing a podspec for submission, you should make sure to do the | |||
|
|||
1. Run `pod spec lint`. This is used to validate specifications. Your podspec should pass without any errors or warnings. | |||
2. Update your library to use [Semantic Versioning](http://semver.org/), if it already does not follow that scheme. See our [wiki on cross dependency resolution](https://github.com/CocoaPods/Specs/wiki/Cross-dependencies-resolution-example) for more details. Essentially it makes everyone's life easier. | |||
3. Make sure any updates you submit do not break previous installations. Adding version `1.1.3` to your library's folder in the Specs Repo should not remove any previous versions. | |||
3. Make sure any updates you submit do not break previous installations. | |||
4. Perform manual testing of your Podspec by [including the local Podspec](/syntax/podfile.html#pod) in the Podfile of a test project, and ensuring it works as expected. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you make this “of a real application and/or your demo application” ? And maybe also add something like “To be clear, only you are responsible for your podspec functioning properly for your users.”
Other than that it looks good to me! |
👍 yep no problem. I'll do that either tonight or tomorrow. |
Done. |
Thanks! |
Updated Specs and Specs Repo guide for Trunk. #5