> For the complete documentation index, see [llms.txt](https://docs.snomed.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snomed.org/snomed-ct-user-guides/simplex-user-guide/how-to..../release-an-extension-in-simplex.md).

# Manage Releases in Simplex

## Simplex Release Cycle Overview

The Simplex release cycle is organized into three sequential stages that guide an extension from active editing through to publication, see the diagram below.

1. **Editing**
   * This is the active development phase.
   * Key activities include:
     * Dependency configuration (linking to a parent or international edition and updating dependency versions).
     * Content development, where content managers upload and modify extension content.
     * Validation, where automated checks are run to identify issues (with the ability to rerun validation if errors occur).
     * Review, allowing users to inspect changes via a daily build and download reports (e.g., XLS).
   * Any system or validation errors must be resolved before moving forward.
2. **Preparing Release**
   * This stage begins once editing is complete.
   * It focuses on:
     * Release validation, ensuring the content is technically and semantically sound.
     * Final content review, confirming that all changes are correct and approved.
   * The release cannot proceed until these checks are completed and content changes are approved.
3. **Release Ready for Publication**
   * The final stage before completion.
   * Includes a technical review to confirm the extension meets publication requirements.
   * Once ready, the extension can be published, completing the release cycle.

<figure><img src="/files/1LPgizxWqXNwEZihDQMb" alt=""><figcaption><p>Simplex Release Process</p></figcaption></figure>

### Accessing the Release Cycle in Simplex

1. Open your extension in Simplex.
2. From the left-hand menu, select Manage Edition.
3. The Manage Edition page displays the current release cycle, showing progress from editing through to publication and providing access to validation, review, and release actions.

<figure><img src="/files/MyL0izVLvBtwo6tbF05U" alt=""><figcaption><p>Accessing the Release Cycle Area</p></figcaption></figure>

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SNOMED+Guide&#x26;entry.670899847=Release%20an%20Extension%20in%20Simplex" class="button primary">Provide Feedback</a>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.snomed.org/snomed-ct-user-guides/simplex-user-guide/how-to..../release-an-extension-in-simplex.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.