Author: Atakan Akbulut
We regularly update our real estate software, introducing new features, improving existing modules, and making changes based on feedback from our users.
Until now, we've used version numbers such as 1.4.148 and 2.0.78. Over time, however, we found that these numbers were not particularly informative, either for our users or for our own team.
That's why we're switching to CalVer (Calendar Versioning), a versioning system based on release dates.
When we released version 2.0 of our real estate software, we introduced several major features, including:
We continued adding new features without introducing another major version number:
We also released approximately 90 smaller updates.
Under the previous system, deciding which changes justified a new major version wasn't always straightforward. For example, should a new integration move the software to version 3.0, or should we continue with 2.1?
A number like 2.0.78 also gave users no clear indication of when the software was last updated.
As we plan further integrations, including virtual PBX systems, Facebook, Telegram, WhatsApp voice calling, and business email management within the CRM, we wanted a clearer way to number our releases.
Our new version numbers will follow a Year.Month.Release format.
For example, releases published in October 2025 will be numbered as follows:
25.10.1 — First release in October25.10.2 — Second release in October25.10.3 — Third release in OctoberWhen November begins, the numbering will start again at 25.11.1. Similarly, the first release in December will be 25.12.1.
This makes it possible to identify the year and month of a release directly from its version number.
CalVer (Calendar Versioning) is a method of numbering software releases according to the calendar.
Our format consists of three parts:
Under this system, a higher version number doesn't necessarily mean a larger update. Both a minor bug fix and a new integration will receive a version number based on their release order.
We'll continue publishing release notes separately so users can see exactly what has changed in each update.
No. The new versioning system only changes how we name our software releases.
Existing features, user accounts, and data will not be affected by this change. Only the format of the displayed version number will be different.
For example, when you see version 25.10.2 in the software, you'll know that it's the second release published in October 2025.
Our REST API versions will continue to be managed independently of the software's release numbering.
For example, API endpoints such as /api/v1 and /api/v2 will not change simply because we're adopting CalVer.
Existing API integrations will therefore not require any modifications solely as a result of this versioning change.
Any future changes to the API will be handled separately from the software's general release numbering.
We'll continue developing our software, improving existing features, and introducing new functionality. Our development process remains the same; only the way we number releases is changing.
We want users to be able to identify which version they're running and when it was released without having to look up additional information.
At Alanya Digital Solutions, we'll continue sharing software updates, improvements, and release notes as development progresses.