Sandbox-to-production release planning and deployment validation
Key Takeaway
Build and test changes in sandboxes, validate in production, then quick deploy the validated job at a planned time.
Sandbox-to-production release planning means building and testing changes away from the live org, moving them through a series of sandboxes, and then releasing them to production at a planned time. Deployment validation is a rehearsal that runs the tests a deployment would run and checks for missing or invalid metadata, without committing any changes. Together they keep production stable and limit disruption for users.
Where to make changes
Make and test changes in a dedicated development environment, such as a sandbox or scratch org, not directly in production. Some changes, such as writing Apex code, must be made in a development environment.
Even small production changes can cascade. For example, changing a field's type can irreversibly alter data or cause Apex code to recompile.
Some administrative tasks are acceptable directly in production, because they manage existing configuration or user access rather than build apps. Examples include:
- Developing email templates
- Creating or editing users
- Creating or editing permission sets and profiles