Improved fastlane git flow release cycle.

[levibostian]

Problem:

• I create a bug fix. I make a beta release of the app. It takes 3 days or so to get approved by Apple (because I have external beta testers). Then, I beta test it, and after assserting no bugs in this release I a prod release and wait another 3 days to get approved all for the same code base.

This is what I want to do:

• PRs from development to beta branch is for internal testing only. This gets approved instantly which is awesome. (I can use the fastlane signup webpage thing to register devices for internal beta testers). I use the com.whatever.foo.beta version of app with internal testers to do a real beta test to make sure everything is working. Then I can have clients test fixes right away without waiting.
• Then, I make a PR from beta to production branches. This creates an iTunes release. Normal prod that takes a few days to get approved.

I could then create another branch, optional, for releasing to external beta testers. This would probably be a com.whatever.foo type of release which is just like a prod release. Then, once that is beta tested successfully I can simply promote it to prod in itunes connect. I can create a new branch in git to do this trigger.

[levibostian]

I have put more thoughts into this and will be doing it in a different way.