Axero Version | Axero Documentation

Version numbering is a crucial aspect of software development, providing a standardized way to identify and track the evolution of a product over time. It aims to provide users with a clearer understanding of software versions, allowing them to easily determine feature availability. The below explains the elements of our versioning scheme and how version information is presented to users.

Axero is a Single Tenant Architecture, meaning you get your own instance of Axero, separate from other customer sites. Your files and databases are separate from other sites. It also means that your site might be on a different version than other sites and may not have all of the latest document features.

Twice a year, typically in the 2nd and 4th quarters, we release a new version for all sites (we call this a "General Release"). In between, we provide "limited" or beta releases for clients willing to access new features earlier and participate in beta versions, understanding there are likely to be more issues with these releases.

Check out our Release Notes to learn about major features added in each version. For a full list of fixes and new features, visit New Enhancements

Check out our Cloud Site Upgrades to learn more about our upgrade process.

Version Display

Version information is displayed in the following format: 9.42.1.20240601. This format allows users to easily identify the version of the software they are using and understand its context within the development cycle. Each part of the version number corresponds to the components outlined below: product number, sprint number, release number, and build date. 

Version Numbering Scheme

Axero's version numbering scheme consists of four main components:

1. Product Number:  This represents the major version of the product and is incremented when significant milestones or changes occur. For example, Version 9 signifies the ninth major release of our product.
2. Sprint Number: The sprint number corresponds to our sprint planning and development cycles. It provides a clear communication standard between development teams and clients, allowing for easy reference to specific development iterations.
3. Release Number: The release number indicates the specific iteration of a release within a particular sprint. It helps track the progression of development within each sprint cycle and distinguishes between multiple releases within the same sprint.
4. Build Date of Release: The build date of the release is represented in the YearMonthDay format, providing a precise timestamp for each release. For example, "20240601" indicates a build date of June 1, 2024. 

Version Information

View your Axero version and the last time your intranet was upgraded.

Examples and Use Cases

Updating Software: Users can check the version number to determine if a newer version is available and decide whether to install updates.

Identifying Feature Availability: Documentation may indicate feature availability based on specific version numbers, helping users understand which functionalities are included in each release.

Troubleshooting Issues: Users can reference version numbers when reporting bugs or issues, allowing support teams to identify the context of the problem and provide appropriate assistance.