Review rollout timing requirements provided by issue creators
Determine the actual rollout schedule based on:
Business impact assessment
System maintenance windows
Traffic patterns and downtime considerations
Dependencies on other deployments
Execute the scheduled rollout at the determined time
This separation of concerns ensures that developers focus on creating quality migration scripts while experienced operators handle the critical timing decisions for production rollouts.
If there are any warnings or errors, as long as you check Rollout anyway, you can still schedule the time.After you schedule the rollout, it will be in the pending state. You can’t manually run it nor edit the SQL unless you click Cancel.After clicking Cancel, you may edit the SQL and restart the rollout process either immediately or schedule it to a later time.
This workflow ensures proper separation of responsibilities: developers focus on creating quality migration scripts, while approvers and releasers handle the rollout timing and execution decisions for production deployments.