docs: decisio-record abour versioning scheme

[paullatzelsperger]

WHAT

Adds a decision record outlining changes to the versioning scheme and release cadence.

WHY

documentation, transparency

FURTHER NOTES

List other areas of code that have changed but are not necessarily linked to the main feature. This could be method signature changes, package declarations, bugs that were encountered and were fixed inline, etc.

Closes # <-- insert Issue number if one exists

[ndr-brt]

Only note: upstream currently doesn't have such a clear versioning scheme, so referring to the the point 4 of the Backporting fixed:

Tractus-X EDC must request that an upstream bugfix version be released. This upstream bugfix can then be incorporated into the Tractus-X EDC bugfix version.

currently this won't be achievable (in an easy way), so maybe it worth discussing about this on upstream as well

[paullatzelsperger]

Only note: upstream currently doesn't have such a clear versioning scheme, so referring to the the point 4 of the Backporting fixed:

Tractus-X EDC must request that an upstream bugfix version be released. This upstream bugfix can then be incorporated into the Tractus-X EDC bugfix version.

currently this won't be achievable (in an easy way), so maybe it worth discussing about this on upstream as well

there isn't a process for it, but it has been done in the past. the understanding is, that if a project, such as T-X, requires a bugfix release, they have to take care of it upstream.

[lgblaumeiser]

lgtm