Define a release as stable

[tobias9931]

Is your feature request related to a problem? Please describe.
At the moment the latest “stable” version is very old and people who are not familiar with it and are unsure are using this ancient version.

Describe the solution you'd like
I would suggest adding the label “stable” to version 1.1.32?
This version ran fine as far as I know and does not yet contain any futuristic code for the new Bootsrap UI

[DaanSelen]

This has already been touched in the monthly meetings, but this is being worked on if I am correct. We're just looking at which version.

[si458]

@DaanSelen this is correct, it was mensioned last months meeting i believe?
@Ylianst has control over the stable/latest tags in NPM so we leave it to him to decide when to do things 👍

[NewUserfromDE]

+1 for the issue
+1 that we discussed it at the monthly meeting - and should continue discussing

Abstract: The main idea was to mark a release as stable, if enough "members" use it without problems. This idea was based on the community module idea, since there are no statistics yet.

So I suggest:

• for a fast remedy and to boost image define some release as stable which is according to experience and talks "stable", so it don't has to be 1.1.32, since anything is better than the very old "stable" one
• for a permanent solution I still second the statistics idea which is part of the community module idea

Please also note:

• see "Concept: MeshCentral Community Meetings", chapter I) 2 d) "Surprise" Concept: MeshCentral Community Meetings #6727 for side effects / once in a life time opportunities regarding version numbers - which also concerns in a wider sense to marking something as stable
• @Ylianst "Community Module" is not just telemetry, it's way more and it's terribly effective (you will have to wait for more explanation, just wanted to tell, since I'm a bit limited at the meetings because of my decision to only text chat during recordings)