All qCrop services and components are developed and released with a common version number.
qCrop major versions are projected for release twice a year, one by the end of March, one by the end of September. Major versions typically introduce new features and might come with significant changes in the underlying architecture of qCrop, the integration APIs, the deployment options, the qCrop metadata format and user interface(s). APIs are kept backward compatible at least for the last two major versions (= one year). Any changes that will break backward compatibility at some point in the future are announced well in advance in the Release-Notes.
Any number of minor versions might be released between the major versions for the purpose of security and bug fixes or for the introduction of highly anticipated new features. Minor versions are generally not breaking compatibility of APIs.
The qCrop version number consists of three numeric parts:
- The first part represents the last two digits of the release year.
- The second part represents the month of the release, either “03” for the March release, or “09” for the September release. The first and second part of the version number together form the major version number.
- The third part represents the counting number of minor versions within the major version. It starts from “001” with each new major version.
According to this rules, the current version of qCrop is 20.09.001.
The Release Notes use the following icons for the individual changes:
- New Feature.
- Known, unresolved issue.
- 20.09 (2020-09-15)
Until mid 2020, qCrop has been developed and marketed as “KIMEcrop”. KIMEcrop had a different versioning scheme and was released in two major versions (1 and 2). qCrop is backward compatible with both KIMEcrop versions. Images that were provided with KIMEcrop cropping hints, and therefore contain the KIMEcrop metadata format, are automatically converted to the most recent qCrop metadata format.