Clarify Release Process

[arnoweiss]

There is still no clarity toward the versioning of commits. The updated docs represent the policy I remember agreeing upon a while back which was never properly documented and adhered to during developement. We should however be very clear to avoid confusion such as here.

[arnoweiss]

Oh and the fact that developement was way behind main is another sign we should clarify the development process.

[mjacoby]

I wholeheartedly agree that we need to clarify the development and release process.
However, the current commit still looks inconsistent to me. I see two options

1. work on development, once a set of features/bugfixes that is release-worthy has accumulated, make PR from development to main which triggers CI to release to maven. Push to development should release to Github. Problem: We are not generating a tag corresponding to the release, i.e. we are "loosing" the code basis of the release.
   Possible solution: add creating tag to CI release action
2. abandon development and work directly on main but change CI to only publish to maven on tag. Push to main should release to Github.

Current PR mixes both approaches as it uses development but triggers release only on tag.
Please change PR to implement one of both approaches.

[mjacoby]

This does not match what is in the description, i.e. that a push on main triggers a release to maven central. However, I agreed that we should only trigger releases upon tags to ensure we have properly archived the code base for each release.

[sebbader-sap]

@alw-iwu @mjacoby if this issue is still relevant, please open a new ticket at https://github.com/eclipse-digitaltwin/aas4j. I will close this one next week.