Skip to content

Planning

Sven Biellmann edited this page Oct 24, 2023 · 5 revisions

For the versioning management we use semantic versioning. If you need more information please consider our API versioning Wiki page.

Versioning Planning

Versions will be planned one year ahead. Every end of year, November, a Version Roadmap will be defined as in the example. This planning includes:

  • Major versions with release date
  • Minor versions with release date
  • optional: planning of features of specific releases

All parties are bound to the defined Major release dates. Minor release dates can be omitted or postponed if there are justified reasons. Bugfix release are made ad-hoc whenever they are needed.

Version Release

When a scheduled release date is reached the following steps are performed to ensure a reviewed and high quality release:

release-timeline

  • 3-4 weeks before planned release: Prefinal version for review provided to all community members. This consists of the different issues to be included and closed with the next release.
  • 2 weeks before planned release: Deadline for feedback from community members to planned release.
  • 3 days before release, optional: Release draft will be created and 'go' collected from all community members.
  • On the day of release: Release will be published.
Clone this wiki locally