> For the complete documentation index, see [llms.txt](https://docs.ozone.one/ozone-end-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ozone.one/ozone-end-user-guide/documentation/ci-cd/catalog/releases-templates-and-runs/what-are-releases-composed-of-pipelines-and-approvals.md).

# What are releases composed of (Pipelines & Approvals)

At ozone, Releases are composed of a set of pipelines.\
Let us consider an example how a typical release looks like:

1. Cloning
2. Testing
3. Scanning
4. Image build
5. Approval jira/slack
6. Deploy.

Here, At Ozone we have a set of pipelines defined in the catalog so that you can directly use these pipeline templates for running the above pipelines. This is how you Create a successful release.