You donāt have new features every 3-4 months anyway as the release schedule is completely out of the window anyway (have a look at the number of days between releases - or did you not even look at the graphic before posting?). And just releasing the bug fixes more often while still releasing new features at a fast rate does exactly nothing to change the situation.
Features should be released when they are ready. That is simply not the case with Xojo.
What I mean is that I would like to see bug fixes every 30 days regardless of if new things are ready to release. I donāt like waiting for new features to be ready to get bugs fixed. Whenever they want to release new features is fine (wasnāt their original intention every 90 days?), but do bug fixes in between.
Which isnāt significantly different from what we have now - or how do you expect this to make Xojo a quality product again when you add a heap of new bugs every three months?
If people are not serious about putting quality and stability over features but only want to tinker on the edges, then forget about Xojo improving. Xojo will then not remain a beta quality product but will go down to alpha quality status.
It was obvious back in 2005, it is obvious now. It really isnāt rocket Science.
One release does not a trend make - yet
Lets see if that continues
Iād be ok with regular bug fix releases - a tick tock schedule
bug fixes
features
bug fixes
features
something different
basically try SOMETHING to quell the angst rather than just push ahead thinking the worlds fine ?
originally yes
then it shifted to quarterly
now I dont think there is any firm commitment for any time frame
Currently itās not quarterly.
Itās more variable and I have the feeling for the last releases, they had a release date in mind, but then delayed it for weeks to get some important things fixed. Putting more effort to ship something working.
And there is an emphasis on not breaking something last minute.
So something fixed a week before r2 shipped did go in, but waited for r2.1 (or r3) to give it time to be tested and not break other things.
I completely agree that last minute changes before a release are to be avoided, especially with Xojoās bad reputation of releasing stuff that hasnāt been tested (enough) before releasing. Many open source projects have a better QA than Xojo (do they even have a procedure? 
) For a commercial product, it is certainly inadequate and if I would release a buggy app like that to the public, Iām sure I would be put up on the spot and get a serious scolding (at the very least!).
Bad management leads to low engagement. Low engagement leads to declining productivity and quality.
Forgive me sire
Based on your observations, if the RRM was introduced in 2005, how was there three years of no problems then all of a sudden the RRM was a bad idea?
Do you not know how accumulation works? Like compound interest? Or a virus spreading? It seems to be harmless but keeps accelerating all the time. It isnāt growing in a linear fashion, but exponentially.
That is the basic problem. A bug? I can work around it. You have another bug? You can work around it. But as the number of bugs increases more and more features just donāt work, and more and more people can no longer work around them - especially those that use it more than others.
People who havenāt reached that stage blithely say āIt works for me.ā ā¦ until it doesnāt any longer. But the weight of the bug burden has an effect on the tool itself. Over time people reach that stage of Xojo no longer working for them earlier and earlier, simply because more and more bugs exist in the tool. And more and more bugs are serious ones.
Itās death by a thousand paper cuts. After a while some of those cuts bleed badly.
And the RRM was ALWAYS a bad idea, the same way that letting a virus spread because āitās just a few peopleā is a bad idea.
At least in NZ they know that the discovery of ONE case means there are more undiscovered cases, and that an immediate nationwide lockdown is necessary to get on top of it. In the meanwhile the ignorant and stupid mock that it is ājust one case and they shut everything down?ā, parading their ignorance as if it is something to be proud of.
The similarities to Xojo are more than skin deep.
And just for the record: a day later 10 more positive COVID-19 cases of the Delta variant have been found, with people having been to schools, lectures, cinemas, supermarkets, on flights, travelling, etc.
Still laughing? Still thinking it was an overreaction?
The stupidity of people is mind-boggling ā¦
As is your apparent arrogance
Yes I do, but I donāt understand how you can link the accumulation of bugs to the requirement for emergency patch releases yet there was none for 3 years or somehow at the 3 years mark everything just started breaking. I donāt have the patch notes from before 2010r2 which is why Iām trying to understand what youāre saying here, but I donāt believe the the papercut analogy when it comes to the need to put out emergency patches or bugs somehow reaching critical mass that everything just broke there after.
During those three years:
After the three years:
E.g. If 1 in 10 tweaks/features need an emergency patch and we only do 10 tweaks itās pretty rare we need an emergency patch, but if we change 100 things then odds are that weāll need an emergency patch. The relationship between tweaks/features to emergency patches hasnāt changed, weāre just touching more stuff now so it looks like we need more emergency patches.
Doesnāt change the fact that some people write REALLY stupid things.
And you keep it going here I see, I might be inclined to think that YOU think you have a ceartain level of intelligence that others on thesee boeards dont haveā¦
Its okay to complaint, but you take that to a different level, and insulting people in the process. That tells something about you, that is for certainā¦
From the confusion caused in the docs, it is clear that in this case the API 2 desktop controls had been planned for r2 but were delayed until r3 now. As far as that goes:
@MarkusWinter , I feel your chart is missing a sh*storms caused by language changes counter.
Because complex systems have synergistic effects that in the case of ābugsā (in biological systems thatās harmful mutations) lead invariably to catastrophic breakdowns. Thatās the reason why Evolution invented sex to weed out negative mutations.
I presume you have read about chaotic systems, and how tiny changes can lead to massively different outcomes? Consider bugs like increases in the chaotic load of a complex system.
Another complex system is the Earthās climate - which has positive and negative feedback loops interacting with each other. Single disturbances wonāt change it much - but accumulation will throw the whole system off balance, and can trigger runaway processes and pass āpoints of no returnā.
In short: when systems reach a level of complexity then little effects tend to NOT add up, but to potentiate each other.
Now you still look for a single major change like a climate change denier doesnāt believe āa bit of human CO2ā could change the climate. But that is not how complex systems work (and software can easily get complex).
And that is the simple reason why I was able to predict in 2005 what would happen with Xojo. Because I worked with several complex systems (virus infections, antibiotic resistance, cancer development) and developed a certain understanding for them. You really have to stay on top of them because any small change can throw you out of whack (like the Covid variants are doing). And Xojo did not stay on top of their bugs.
Oh, I have no doubt that there are more intelligent people around here than I am. I just wish they would use that intelligence more often. How about you try it? 
Had to meet a deadline so no time for that, but feel free to improve on it. After all, I have it on good authority that Iām not the smartest cookie around here 
Iām not sure Iām up to it 