Release process

Releases should be coordinated

In mapbox-sdk-py

• Release branch from master
• Update version in mapbox/__init__.py
• Update CHANGES
• Create a Release ticket
• Commit, PR, review and merge it
• Checkout master and pull
• git tag version where version is a major.minor.patch string and git push --tags (Travis releases for us)
• Close release ticket

In mapbox-cli-py

• Wait for new sdk version on pypi (otherwise cli might be published to pypi and, for a short time, have a dependency on a sdk version that doesn't exist yet)
• Release branch from master
• Update version in mapboxcli/__init__.py
• Update SDK version spec in setup.py
• Update change log
• Create release ticket
• Commit, PR, review and merge it
• checkout master and pull
• git tag version where version is a major.minor.patch string and git push --tags (Travis releases for us)
• Close release ticket

In homebrew-cli

Follow https://github.com/mapbox/homebrew-cli/blob/master/release_docs.md