Unclear release versions and tags #420
Description
Unfortunately, I'm not quite sure how to interpret the repository / tags / releases and version variables int the entire VerneMQ project correctly.
I have some questions here and would be thankful for any answer:
- Do you version the VerneMQ version, Docker image version and Helm Chart version separately? Or is this a one-to-one match?
- How are docker images and helm charts built? How does the tag correlate to a specific commit of this repository?
- The latest release and tag of this repo ist from Jun 19, 2024 - 2.01
- The "latest" tag on Docker Hub also resolves to the over-a-year-old 2.0.1
- The master branch suggests the newest tag is 2.1.1
- The newest tag on Docker Hub is 2.1.2 instead (which is a pre-release - but without any -beta.x or other semantic version postfix)
- Same for the Helm Chart => 2.1.2 is available, but the master branch still shows 2.1.1
- There is a merged rel-2.0.1 branch, an unmerged rel-2.1.1 branch, and no rel-2.1.2 branch
This raises further questions:
- Are your tags all rolling tags on Docker Hub? Does the digest of the 2.1.2 change after VerneMQ is out of the pre-release stage?
- Is your actual "latest stable" version the 2.0.1?
- Do the rel-x.x.x branches correlate to the docker hub / chart index.yaml releases instead?
- Will there be further releases at all in the docker-vernemq repository, or is it just used as build script for "just in time manual builds"?
In my opinion the project would benefit from either
- Splitting at least the chart version from the application version + the introduction of some kind of immutable tags - the same one for docker images and this repository
- A clarification in the README about how to interpret the versions and tags
Thank you!