> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.1/getting-started/ovaledge-release-cadence.md).
# OvalEdge Release Cadence
OvalEdge follows a structured release cadence to deliver new features, product fixes, and resolutions to critical issues. Releases are categorized as **GA Releases**, **Patch Releases**, and **Emergency (HotFix) Releases** based on the scope and urgency of the changes.
## Release Versioning
The release number indicates the type of release:
| Version | Release Type |
| ----------- | -------------------------- |
| **8.1** | GA Release |
| **8.1.1** | Patch Release |
| **8.1.1.1** | Emergency (HotFix) Release |
## Release Types
### GA Release
**Example:** Release8.1, Release8.2
**Frequency:** Quarterly
A GA (General Availability) Release is the primary product release.
**A GA Release may include:**
* New features and enhancements
* Library and dependency upgrades
* Defect fixes from the product backlog
* Other planned product improvements
**Testing:** A GA Release undergoes a complete regression testing cycle.
### Patch Release
**Example:** Release8.1.1, Release8.1.2
**Frequency:** Sprint-Based
A Patch Release delivers product fixes within a sprint-based timeline.
**A Patch Release may include:**
* Product defects
* Fixes reported by multiple customers
* Typically, Priority(2) and Priority(3) issues
* A combination of fixes delivered together
**Testing:** Patch Releases undergo impact-based testing based on the changes included in the release.
### Emergency (HotFix) Release
**Example:** Release8.1.1.1
**Frequency:** As required
An Emergency (Hot Fix) Release provides a dedicated fix for a critical issue that requires immediate resolution, typically to unblock a customer.
**An Emergency (Hot Fix) Release is primarily used for:**
* Priority(1) issues
* Critical customer-blocking issues
* Issues that cannot wait for the next planned release
**Testing:** The fix undergoes targeted validation based on the change's scope and impact.
***
Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.ovaledge.com/release8.1/getting-started/ovaledge-release-cadence.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.