RELEASING.md

(Somewhat) automated process:

1. Start a git-flow release/x.y.z
2. Create a CHANGELOG.latest.md with the changes for the current version (to be used by Fastlane for the github release notes)
3. Update the version number by running bundle exec fastlane bump_and_update_changelog version:x.y.z
4. Commit the changes git commit -am "Version x.y.z"
5. Make a PR, merge when approved
6. cd bin
7. ./release_version.sh -c x.y.z -n a.b.c, where a.b.c will be the next release after this one. If you're releasing version 3.0.2, for example, this would be ./release_version.sh -c 3.0.2 -n 3.1.0. This will do all of the other steps in the manual process.
8. Make a PR for the snapshot bump, merge when approved

Manual process:

1. Create a branch bump/x.y.z
2. Update the version number in RCPurchases.m, Purchases.podspec and in Purchases/Info.plist by running fastlane bump version:x.y.z
3. Update CHANGELOG.md for the new release
4. Commit the changes git commit -am "Version x.y.z"
5. Make a PR, merge when approved
6. git tag -a x.y.z -m "Version x.y.z"
7. git push origin bump/x.y.z && git push --tags
8. pod trunk push Purchases.podspec
9. carthage build --archive
10. Create a new github release
11. Upload to the new release Purchases.framework.zip
12. Create a branch bump/a.b.c, where a.b.c is the next version of the app after this release.
13. Update the version number in RCPurchases.m, Purchases.podspec and in Purchases/Info.plist to the snapshot version for the next release, i.e. x.y.z-SNAPSHOT
14. git commit -am "Preparing for next version"
15. git push origin bump/a.b.c
16. Make a PR for the snapshot bump, merge when approved