Who is responsible for a release?

Responsibility for a release depends on the team's structure and level of automation, but in modern processes three key parties are usually involved: developers, QA, and DevOps (or the Release Manager).

---

#1. Developers (Dev Team)

• Prepare the code and make sure it passes all the CI/CD stages.
• Are responsible for the quality of their change: tests, documentation, compatibility.
• Once CI is "green", their code becomes ready for release.

---

#2. QA / Test Engineers

• Verify that the new version is stable and meets requirements.
• Confirm that the build can be shipped, especially during manual smoke or regression testing.
• In Continuous Delivery, they usually take part in the final "go/no-go" decision.

---

#3. DevOps / Release Manager

• Manage the release pipelines and environments (staging, production).
• Make sure the release is carried out safely: without downtime or data loss.
• Monitor the system after the rollout and roll back the version if needed.

---

#The modern approach

In Agile and DevOps teams, a release is a shared responsibility.

• The Product Owner decides what and when to ship.
• The development and testing team guarantees quality.
• DevOps ensures a reliable technical rollout.

---

#Conclusion

A release is not the responsibility of one person, but of the whole team: developers for the code, QA for quality, DevOps for delivery. Together they make sure the release is safe, reproducible, and manageable.