Allow sequential approvals to be required before starting deployment
Proposal
Currently, deployments can require approvals but the approvals don't need to in any order. Maintainers in a project can approve out of order. In organizations that follow a two-person concept, this can mean the deployment can start at a time other than desired by the second person or stakeholder.
An example:
DeveloperManager from Project needs to approve a deployment to verify that the correct commit has been marked and all code has been reviewed. ServerAdmin needs to review the deployment, arrange a downtime schedule and "push the red button." The order must go DeveloperManager -> ServerAdmin -> deploy.
Currently, these approvals can go out of order where ServerAdmin approves before DeveloperManager