"Stable" vs "Nightly" builds

[EspoTek]

Given the recent issues with macOS builds breaking, I think it wouldn't hurt to have a manually curated "stable" release that includes versions that are known tested/working, even if a few months out of date. This way, if the nightly breaks for whatever reason, at least new users can download something.

[mi-hol]

Makes perfect sense. Any volunteer to address this and #354 ?

[EspoTek]

I'm happy to get this put in place once the mac builds are back.

[mi-hol]

@EspoTek the latest pre-relase build from commit 6b4937c had over 200 downloads by now and no new issues.

May I suggest to tag it as "v2.0.0-beta" ?

Assuming no further major issues surface in the comming 2 weeks, we could change its status from "pre-release" to "latest release".

Any comments welcome.

[mi-hol]

ping

[EspoTek]

pong. :)

I've updated continous to be marked as regular (not pre-release) and made the stable one here:
https://github.com/espotek-org/Labrador/releases/tag/stable

We can just update it occasionally with tested releases.

[mi-hol]

I've updated continous to be marked as regular (not pre-release)

That was an unexpected reaction to my proposal.
I expected only a comment related to "are we close to a new release"

From the change my understanding is now "yes, a new release is ready"

The open question I see is "How should a release be communicated & flagged to the public?"

More and more people understand the concepts related to "semantic versioning" hence my proposal to use "v2.0.0-beta".
The number of downloads is NOT an indicator for the quality of software, hence I intended to flag the actual state via "beta" and wanted to trigger more feedback from the user base.

@espotek-org/maintainers is this a topic for further discussion in the team?
I'd take no response as a "not needed".

[EspoTek]

The main reason I did that is due to UI differences. For pre-release stuff, it hides the Assets beneath the dropdown menu, whereas for a regular release they're visible by default. If we're trying to suggest to the user "download this one" we don't want to put the download links out of view.

Regarding the tag, I think "continuous" makes sense. Since 2018ish or so there have been no real version milestones, just constant development and improvement. And frankly we don't have the QA resources to do proper versioning Calling it "2.0.0 beta" might imply that the older releases (1.1) are more thoroughly tested or stable, which honestly they aren't.