Release Cycle

From Veridu

Backward Compatible Changes

Backward Compatible Changes - BCC -, are changes that won't affect the current product (e.g. the API), behavior.

BCC are deployed using a Rolling Release Cycle, in other words, BCC are deployed every day.

Note that Customers/Licencees are not notified about every BCC deploy.

Bug fixes, new features and software-related performance enhancements are covered by BCC deploys.

You can find additional details on our Release Cycle on the Project Management article.

Backward Incompatible Changes

Backward Incompatible Changes - BIC -, are changes that affects the current product (e.g. the API), behavior.

BIC are deployed using a Standard Release Cycle, in other words, BIC are deployed based on a schedule.

All Customers/Licencees will be notified about BIC deploys by e-mail (registered contacts on our Dashboard) and release schedule will be available on Version article.

BIC releases follows the rules below.

Changes that affects one or more API end points behavior

This kind of change will result in a minor version bump (i.e. the number 3 of 0.3), leading to a new API URL (e.g. https://api.veridu.com/0.4/).

After a minor version bump, the previous version will be deprecated and within 3 weeks it will be fully disabled.

Changes that affect API behavior

This kind of change will result in a major version bump (i.e. the number 0 of 0.3), leading to a new API URL (e.g. https://api.veridu.com/1.0/).

After a major version bump, the previous version will be deprecated and within 3 months it will be fully disabled.

Legacy Versions

Legacy versions are product (e.g. the API) versions that went deprecated but had an extended lifetime due to Customer/Licencee paid support before being fully disabled.

Products running in legacy mode will only receive bug and security fixes/maintenance.