Add existing Archive Sets to a 'Release' CSR (improved process for Mass Migrations)

I would like to see the ability to manage approvals and migrations of a release based mass migration in a more controlled way.

• 'Releases' are typically reviewed and approved by the 'important people' in a project/organization, they tend to have no idea what it is they are approving.. 
• Providing them with a looooong list of CSRs will only confuse them, resulting in endless questions about things they don't understand..

Ideally I would be able to:

• Create a separate CSR Type for 'Releases'
• Define a separate Workflow for these 'Releases'
• Define a separate Migration Path for these 'Releases'

So far, so good..

Now to make this work, I should be able to attach existing Archive Sets to this 'Release CSR':

• Instead of creating a new Archive Set, click on the 'Release' button
• Then select the SCR/Archive Sets you want to include in this new 'Release CSR'

This will also make hand-offs between parallel projects a lot easier, the deliverable of the project would become a 'Release'. The production support team will then be able to pick up that Release, attach it to a new CSR and have it follow the default migration process/path to production.