Deployment and updates

Strategy

Each new feature(s) will be released to our production and sandbox environment once tested and approved. Expect changes on a daily basis

• Each new build will get a new build version
• Each new release will get a new version (x.y.version)
• Each new release with new functionalities will get a new minor version (x.minor.z)
• Each new release with technical breaking changes will get a new major version (major.y.z)

Each consumer is automatically migrated to the latest minor version. In the future we will make this configurable for the end client

You can find the changelog on this page. We document on minor level (1.1.x, 1.2.x)

Migration

Each major version will be actively supported for 1 year at least before it is made deprecated.

Expected Release cycle

Minor versions will be released throughout the supporting period. Major versions may contain technically breaking changes.

Major	Release dat	Actively supported until	End of life
0.x	1/8/2019	-	10/3/2020
1.x	10/3/2020	10/1/2026	tbd
2.x	not planned yet