Release Management Automation

[lucaro]

Since the last release, nobody updated the pre-built version of the UI in the github releases. Could someone have a look at this and how to prevent this in the future?

[silvanheller]

What should the release artifact include? just jar and config-file? Or the entire source code? One way to prevent this is to have a PR template.

[lucaro]

Ideally, there would be a pre-built version for every component of the stack which is known to be compatible to each other. This is especially relevant for the UI (see vitrivr/vitrivr-ng#15 where I copied this from) since having a jdk when you have a jre is probably more likely than having a node environment. We could then link all these released components together on a page on vitrivr.org.

[silvanheller]

The current state is that we'd like two things:

• Automatically update latest on Dockerhub (See Github Actions
• Automatically build & publish releases (always / for certain versions)

[silvanheller]

Thanks @mpas97!