How did your releases go?

Our releases usually followed this process:

1. Release preparation: after completing development and testing features, a release branch is created in the version control system (e.g., Git).
2. Build and testing: on the CI/CD server, build and automated tests are run to ensure stability.
3. Code review and approval: the release branch undergoes a final review, and found bugs are fixed.
4. Deployment: using automated scripts or tools (Jenkins, GitLab CI, Ansible), the release is rolled out to staging, then to production.
5. Monitoring: after release, system monitoring is conducted for errors and performance.

An important part was the ability to rollback the release in case of critical issues. Practices such as canary releases and blue-green deployment were also used to minimize risks.