> For the complete documentation index, see [llms.txt](https://docs.theconfigteam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theconfigteam.com/prebilt-for-public-cloud/upgrading/understanding-release-numbers.md).

# Understanding release numbers

PreBilt for Public Cloud uses a three-part version numbering format:

```
Major.Minor.Patch
```

e.g., 3.5.2

<table data-header-hidden><thead><tr><th width="155"></th><th width="155.199951171875"></th><th></th></tr></thead><tbody><tr><td><strong>Version Element</strong></td><td><strong>Example</strong></td><td><strong>Meaning</strong></td></tr><tr><td>Major</td><td>3</td><td>Significant new functionality, platform changes, or major enhancements that may require additional testing and user communication.</td></tr><tr><td>Minor</td><td>5</td><td>New features, improvements, and enhancements that are backward compatible with existing processes.</td></tr><tr><td>Patch</td><td>2</td><td>Bug fixes, performance improvements, and small corrections with minimal functional impact.</td></tr></tbody></table>

## Typical Upgrade Guidance

* Patch releases should require limited regression testing. This could be upgraded to when possible.
* Minor releases should be tested against key business processes before deployment. This should be upgraded to at the earliest convenience.&#x20;
* Major releases should undergo full user acceptance testing and deployment planning. This must be upgraded to within 6 months of release otherwise some functionality could break, due to SAPs deprecated APIs.