Skip to content
This repository was archived by the owner on Jun 13, 2025. It is now read-only.

Release Number Management

Jump to bottom
anja edited this page Dec 12, 2016 · 4 revisions

The knowledgefinder-core, knowledgefinder-dataimport and the knowledgefinder-webapp are always released together. Therefor they always have the same release number. The example project has its own release number.

How to build the release number

<ConfigurationBreakingChanges>.<NewFeatures>.<Bugfixes>

How to increment the release number

Bugfixes

For Bugfixes and correction of typos: Increase <Bugfixes>

⚙️
 A bugfix would result in a switch from 1.1.4 to 1.1.5.

New Features

New Features are added to KnowledgeFinder, but previous configuration projects still work: Increase <NewFeatures>, reset <Bugfixes> to 0

⚙️
 A new feature would result in a switch from 1.1.4 to 1.2.0.

Configuration Breaking Changes

Changes in KnowledgeFinder, which break the configuration projects. (The configuration projects NEED to be adapted): Increase <ConfigurationBreakingChanges>, reset <NewFeatures> to 0, reset <Bugfixes> to 0

⚙️
 A change in the way the Frontend is configured would result in a switch from 1.1.4 to 2.0.0.

Clone this wiki locally