Why is -beta added to Release and asset names?

[suzuki-shunsuke]

e.g. v2.4.2-beta

The tag name is v2.4.2, but the release name is v2.4.2-beta and asset names include -beta.

e.g. marmot-v2.4.2-beta-darwin-amd64.tar.gz

Why is -betaadded to Release and asset names? If you want to add-beta, how about adding -beta` to tags too?

The -beta looks weird and it makes install scripts a bit complicated.

[maxpert]

I'm intentionally marking at beta. While I have a couple of people who have deployed it out in production, and I have myself been running couple of things in production over it. There would be still bugs, and over each iteration right now, even in the minor versions, I'm breaking a lot of serialization and how data is persisted. I am just being careful passing the message that it's still early, while it works. I don't want people to start putting their financial systems on it unless I've got a provable long record of stability.

[suzuki-shunsuke]

Thank you for the explanation.

I briefly wondered whether -beta might have been added by mistake, or whether it had been removed from the tag, but it’s now clear that this isn’t the case. Thank you for clarifying.

I understand your concern, but since this is OSS, even if a bug were to cause damage to users, the final responsibility lies with the users themselves.
If you want to make it clearer that the project is still under development, I think adding a note to the README would be a good approach.

I don’t think the presence of -beta itself is a problem.
The real issue is that the version notation is inconsistent between the GitHub tag, the release, and the assets.
This could be resolved by adding -beta to the tag as well. Doing so would also make it clearer that the project is still in a development phase.

Possible concerns with adding -beta to the tag include the fact that tags have already been created without -beta, so changing this might cause confusion, and that users might mistakenly think older versions without -beta are more stable.

Anyway, thank you again.
I'll fix our settings of the installation tools.

https://github.com/aquaproj/aqua-registry/blob/77766ab41fc4f07fd25318face0f7f51d233d2bf/pkgs/maxpert/marmot/registry.yaml#L79-L87

[maxpert]

Good callout. I will fix my scripts to make sure tags and releases packages look same.