Versions

Starting with version 25.1.0, Micetro uses a calendar-based versioning model, in which releases are numbered according to the year in which they are released, along with two rolling numbers that indicate the major and minor release numbers within a calendar year. In this versioning model, version numbers are structured as <Year>.<Major release>.<Minor/Patch release>.

For example, in the version 25.1.1:

• Year indicates the last two digits of the calendar year, e.g., 25 means the version was released in the year 2025.

• Major release indicates the sequence of major releases in the year, e.g., 1 indicates that it’s the first major release of the year.

• Minor/Patch release indicates the minor/patch release on top of the major version, starting from 0, e.g., 25.1.1 is the first patch after the release of 25.1.0.

Calendar-based versioning will not be applied retroactively to existing versions, e.g., 11.1.0.

Each release builds on top of the previous version, so any new release contains fixes for bugs and issues that were resolved in previous versions. Patches are only used when specific issues in a particular version need to be addressed. Any fixes applied in a patch will also be part of the next release and any releases in the future.

Version support

Versions are supported for two years from their original release dates. Any patches applied on top of a version do not reset this timeframe, which always refers to the release date for which .0 is the patch number.

If you have any questions, please contact BlueCat Support at support@bluecatnetworks.com.

Accessing documentation for your version

If you’re using a version of Micetro that is not the most recent, you can access the version-specific documentation—including an installation guide, user guide, admin guide, and reference articles—by selecting your version from the dropdown in the upper left corner of the screen.

Because major versions are supported for two years, the documentation for major versions is also maintained for two years.