First and foremost, Hutte promotes the best practice of ensuring that what is deployed to Production is identical to what was deployed to QA sandboxes and thoroughly tested.
With this principle in mind, it’s essential to understand the two possible statuses of a Release record in Hutte and their implications for deployment:
- Draft Status:
- When a release is first created, it is in Draft status. This means the content of the release is flexible and can be modified. For example, new user stories, bug fixes, last-minute changes, or even functionality reverts can be added to the release.
- While the release is in Draft status, it can be deployed to any sandbox for QA purposes. However, deployment to Production is not allowed during this stage.
- Published Status:
- Once QA has been completed in the sandboxes, the release can be marked as Published. This status signifies that the release content has been tested and is confirmed to be ready for Production.
- At this point, deployment to Production is enabled, ensuring that only thoroughly tested changes are promoted.
<aside>
Read more:
Validation Deployments
Test Level Recommendations
</aside>