Skip to content

Latest commit

 

History

History
48 lines (32 loc) · 1.95 KB

RELEASING.md

File metadata and controls

48 lines (32 loc) · 1.95 KB

Releasing Velocidi Objective-C SDK

This is still a draft of the process, it needs verification and a test run in a clean environment to verify everything is in place.

  1. Make sure travis build passed and that the coverage is at an acceptable level.

  2. Choose the version number. Both CocoaPods and Carthage use a form of Semantic Versioning.

  3. Go to VelocidiSDK folder.

    $ cd VelocidiSDK

  4. Edit the version number and increment the build number using agvtool (more info here):

    1. Version number:

      $ agvtool new-marketing-version <your_specific_version>

    2. Build number:

      $ agvtool next-version -all

  5. Go back to the project's root folder.

    $ cd ..

  6. Edit the file VelocidiSDK.podspec with the chosen version number:

    spec.name         = ...
    spec.version      = 0.0.1 # New version number
    spec.summary      = ...
  7. Edit the CHANGELOG.md

  8. Edit the install instructions in README.md so that the example version matches the new version.

  9. Commit the changes. git commit -m "Release v0.1.0"

  10. Tag the commit.

    $ git tag v0.1.0 && git push --tags

  11. Head over to Github Releases, select the pushed tag, and add the copy for the new release from the Changelog to the release body. Give it the title of vX.Y.Z and click "Publish Release".

  12. Deploy the library to CocoaPods. $ pod trunk push VelocidiSDK.podspec

  13. Update the version in .jazzy.yaml

    github_file_prefix: https://github.com/velocidi/velocidi-ios-objc-sdk/tree/v0.1.0
    module_version: 0.1.0 
  14. Deploy the documentation. $ .scripts/deploy.sh