Does submitting a new version interrupt the phased release of the currently live version?

We currently have version 1.2.0 live and in the middle of its 7-day phased release (automatic updates), currently around the 5% stage. We now want to submit version 1.3.0.

I want to confirm the exact behavior before we submit, because I've heard conflicting claims internally.

My understanding is:

  1. Submitting 1.3.0 for review does NOT affect 1.2.0's ongoing phased release. 1.2.0 continues ramping (10% -> 20% -> 50% -> 100%) undisturbed while 1.3.0 is in review.

  2. If 1.3.0 is set to "Manually release this version," it will sit in "Pending Developer Release" after approval and still not affect 1.2.0's rollout -- nothing changes until I actively release it.

  3. Only when I tap "Release" on 1.3.0 does 1.2.0's phased release stop, at which point 1.3.0 begins its own phased release from 1%.

  4. If 1.3.0 were instead set to "Automatically release this version," it would go live the moment Apple approves it and would interrupt 1.2.0's rollout at that point.

Questions:

  • Is the above correct? Specifically, does the act of submitting/approving a new version have any effect on the currently live version's phased rollout, or is the rollout only ever interrupted by the release action?

  • When 1.3.0 is released and 1.2.0's phased release is interrupted, what happens to the users who had not yet received 1.2.0 via automatic update? Do they get queued for 1.3.0 instead?

Thanks in advance for clarifying.

Does submitting a new version interrupt the phased release of the currently live version?
 
 
Q