[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem "Stable" is not stable


In my youth, aaaaaahhem some "months" ago now, there was the alpha or active development "caste" where things could be inserted, removed, changed, broken etc, the "beta" which was the first release candidate where things could be fixed but nothing added and then the pre-release where nothing but cosmetic e.g. speelling mistooks could be correctored and finally a release which was immutable. Perhaps we should go back to those halcyon days on the sides of the Adriatic where every piece of code was cast in stone and by the gods if you got it wrong ....😬

b

On 28/8/24 7:39 pm, Christof Thalhofer wrote:
Hi,

a new user who has registered in the German forum gambas-club.de and is very interested in Gambas has drawn my attention to a problem that I have been aware of for some time:

Users have the impression that Gambas is not stable and that they cannot really rely on the programming language “because there are too much changes in every new version": He gave the website https://www.laurux.fr/ as an example and said that this had been his impression for quite a long time.

I had to do a lot of arguing to convince him that Gambas is stable and the backwards-compatibility of Gambas is really outstanding and much better than many other programming languages.

The reason for his impression is quite simple: What is published on Launchpad under the label “stable” is definitely not stable if the minor version has just changed. In reality, it takes months for the new minor version to become really stable.

At the moment version 3.18 is really really stable!

I think to address this problem we need a different release cycle because what is currently offered as "stable" is often damaging the reputation of Gambas.

So I suggest that we should think about whether it wouldn't be better to label a new version as “testing” and the previous one as “stable” and offer both on Launchpad.

Alles Gute

Christof Thalhofer



References:
Problem "Stable" is not stableChristof Thalhofer <chrisml@xxxxxxxxxxx>