API2 syndrom.
That is unfortunate… I learned a lot by seeing other people’s questions answered in the NUG and forums over the years.
-Karen
Probably a combination of things
Speculating that it could be related to
- xojo employees not answering many threads in the forums
- mvps not participating much
- lots of long time users not participating for whatever reason
Wow. It’s mid-May and Xojo hasn’t shipped anything this year.
a great place to take questions and respond here is always an idea 
1 Like
I’m sure they’d dispute that since 2019r3.1 shipped Jan 23 2020
I think I know what you mean though
Theres been no 2020rX releases so far and its May
I’m sure they want the first release of Web 2.0 to be really complete & really solid
I think that is the problem when you tie year to a release version. They would be better off not having year as part of the version number.
Hopefully there will be a 2020 release in 2020. 
In other words: they don‘t want a rapid release model. Not that they would admit that.
As far as I‘m concerned the Rapid Release Model has been an abject failure.
Did it provide BUGGY features faster? YES.
Did it provide STABLE features faster? NO.
Did it lead to more buggy apps? YES
And that was predicted right at the start.
Time to ditch it.
While they are fixing things in all platforms, they also are focused in finishing the new Web 2.0 and this part is dragging the 2020 release 1 to an unknown future date. Is it possible/feasible to them to “detach” the new Web 2.0 code for a moment, release a 2020R1 with just the fixed things by now + the last stable Web 1.0? Then, they could reattach the current web 2.0 code in development and resume the works.This way, Web 2.0 could come in a 2020R2 and many very broken codes for MS Windows from 2019, could, potentially, run now in a R1 and tensions could decrease a bit.
I would tend to agree that after 15 years it might be time to reconsider as I’m also not convinced that this has worked as well as intended
Delivering well tested fixes & features sooner isnt a bad goal
How to achieve that is whats at question
No ?
I think the anticipation and hype for web 2.0 will not allow Xojo to release 2020.R1 without it including web 2.0.
Hmmmm… .looks like another member of that other forum may have stuck his foot into the hornets nest… I mean… seriously… Xojo (like Trump) doesn’t take criticism (constructive or not) well (or at all for that matter)
Blockquote
Stéphane M
24 minutes ago France
@Geoff P — My main problem here is that there are hundreds of bugs waiting to be fixed for years and yet Xojo would rather give priority to changing method’s names.
If we want to change a RemoveAllRows method by DeleteAllRows, we can do it ourselves. What we cannot do ourselves is to make the compiler better and properly handling cases where it fails now.
So please set your priorities right.
2 Likes
Sounds like last year when everything was put on hold for months on months for API 2.0. I lost months on my License waiting so I didn’t renew which turned out to be a good move. Essentially not much has been updated in a year other than renaming stuff.
Thats a given
2020r1 HAS to include it
Well… Then I’ll forget Xojo for a few months and dedicate more time to other things. 
They fixed few things and broke another set. It’s hard to impossible to find a fully usable, stable, Xojo edition.
And that comment is not visible when I checked.
its still there
at least for now
1 Like
Odd… It doesn’t show for me? Maybe I need to logout and log back in again or something.