> For the complete documentation index, see [llms.txt](https://jframework.gitbook.io/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jframework.gitbook.io/help/versioning.md).

# Versioning

Software versioning is a crucial practice for effective software development and management. It involves assigning unique identifiers to different stages of software development, facilitating easier tracking, and management of software updates, dependencies, and compatibility issues. A standard format for versioning we adopt is based on UTC and structured as `[YYYY-2021].[MM-1].[DD-1].[Release Hour]`.

For instance, if we are scheduled to release a new version at 11:00 on June 6th, 2023, the appropriate version number would be `2.5.5.11`. This structured versioning helps in managing software dependencies efficiently as different versions may introduce varied features, functionalities, or compatibility requisites.

Versioning plays a pivotal role in keeping a historical record of software changes, ensuring each version is well-documented, and tested, and that developers can accurately track software evolution. It also empowers users by providing the flexibility to upgrade to the most current version or revert to an older one if necessary, enhancing overall user experience and software stability.


---

# 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:

```
GET https://jframework.gitbook.io/help/versioning.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.