We use a strict version number tracking of all our code changes. It's loosely based on the semantic versioning standard and helps a lot with our release engineering processes. We display version numbers mostly as an information, although you can't know much about the underlying changes.

Sometimes, we will announce new features, and we'll associate those new features announcements with a version number (for example, we could say "starting at version 3.0, the new user account management interface is now considered stable and is now available to everybody").

The codebase is shared between all our services, but the release process is strictly decoupled. Which means that you see the version numbers for the "website" service, which is usually the service with the fastest pace of evolutions, and other services (like our apiserver, or the spiders) can sometime be a few versions behind. This should have no impact on your usage of Apercite.