Currently its not possible to deliver two versions of the same app towards appsource in parallel. The whole process from preview till go live needs to be completed before publishing a new version to AppSource.

Take for example the following scenario:

• A preview version for your next major/minor is published to appsource
• This version is still in preview and validated by one or specific customers
• Meanwhile a business blocking issue occurs on your production version
• For this version a hotfix is created and published to appsource (Including a go live step)

In the above scenario, the initial submission of major/minor (still able to access if you know the ID), will get the following state: Archived/ReadyToPublish.

Being archived its no longer possible to promote this submission. Only workaround left in that case:

• Resubmitting the major/minor (using same artifacts)
• Promote it when it's re-validated

Proposed solution:

• Keep previous submissions pending (possibly with a expiration date) while other submissions of the app happen
• When promoting the app always provide the submission ID

The above solution can work for APIs. with the UX in partner center there are more challenges to this approach.