Branch Repo Management

[AIMENandresperez]

Hi!
Currently, the repository does not have tagged versions, making it difficult to determine whether the main branch is in a stable development state.
I propose adopting the GitFlow pattern or, at the very least, introducing a develop branch for ongoing development while keeping main reserved for stable releases. This would improve version tracking and provide clarity on the stability of the codebase.

[paullatzelsperger]

MVD is neither a product nor a platform, it is an example of how a minimum dataspace could look like. It lives on the bleeding edge of development and adopters should be prepared for frequent updates. This is on purpose, because MVD also serves as testbed for us maintainers to try out new stuff from upstream. As such, we want it to use the very latest developments.

Those who don't want that can always revert to release versions of EDC (or nightly builds) themselves, it's easy enough to do. However, that is a purposeful act and should not be the default behaviour of MVD. So if you experience a broken build, you can always revert to the last known good nightly. Its just that you yourself have to do that.

A GitFlow workflow might work fine for smaller, single-repo projects, but EDC is quite complex and so is our release pipeline.

That said, I could see a workflow where after an upstream release, we create a tag with all EDC versions pinned to the release. That way, main would still track snapshots, but those who want a more stable version can use the release tag. It would not be a release in the conventional sense, with published docker images and maven artefacts etc.

[AIMENandresperez]

Got it, appreciate the response!