Whither Xojo 2020 Release 1

The Xojo drought we’re experiencing in 2020 is starting to become ridiculous.  The last release, Xojo 2019 R 3.1, was released January 23rd, 2020.  As of today we’re at 152 days.  

The longest previous delay between releases was 143 days between Xojo 2012 R2.1 (January 12, 2013) and 2013 R1 (June 4, 2013).  If I recall correctly this was the transition from Real Studio to Xojo and was when the IDE went through a massive redesign (and ironically I was accused of causing a 6 month delay due to a blog post).

Come on Xojo.  There are plenty of bugs and enhancements that should be shipped NOW.  Is the Rapid Release Model being replaced with once a year monolithic releases?

19 thoughts on “Whither Xojo 2020 Release 1

    • It’s just like me. I too would have liked to hold Release 2 in my hands already for this year. But this cycle seems, hopefully lasting, to modify something in the company structure. If you look at the current betas, it becomes clear that a lot of work is still needed before Web 2.0 can be delivered, although the feature set is already very neat. my opinion But there are still missing functions in the IDE etc. At the same time Xojo uses the time to deal with long open bugs. From my point of view, 2020r1 could be a very pleasant version for us users. Let’s not build up additional pressure, the guys have enough of it anyway 😉

  1. > Is the Rapid Release Model being replaced with once a year monolithic releases?

    One can only hope. But please be honest – the “monolithic” is in reality one major release followed by several bug fix releases resulting in a nicely stable final release before the next big upgrade (as you well know).

    • Hm…well, we’ll see. If it was truly new/major features followed by several bug release cycles (i.e. NO new features) I’d be happier than the perpetual beta cycle we have now.

      • The rapid release model is/was predicated on releasing well tested “production ready” new features and bug fixes to improve the overall quality of the product.

        15 years of the same bitches & complaints about overall quality & perpetual beta would suggest it isn’t working as intended. Originally there was a release every 90 days. Then once a quarter. Now ?

        Perhaps a rethink about the premise of rapid release is in order ?

        Apple seems to do fine with a big release once a year then lots of bug fix releases. MS does much the same (although they dont put a new name on it annually like Apple does)
        Lots of Linux distros fares well with a big release then lots of bug fix releases.

        • “The rapid release model is/was predicated on releasing well tested “production ready” new features and bug fixes to improve the overall quality of the product.”

          Then why was it so easy to predict that we would end up with perpetual beta quality software (and let’s not even bring up the multitude of emergency releases for major bugs)?

          No, the RRC was always driven by features to sell, so it was driven by hype, not by quality / stability. So features got pushed out early in a half-baked state. Which meant you needed a new feature ready for the next release – so even serious bugs (like the socket) never got tackled. Hence why the quality went down.

          It’s not that it wasn’t easy to see and predict – it’s that users willfully looked away (you see the same with Republicans looking away from Trumps sexism, racism, stupidity, etc while it was easy to see that he was going to be a disaster).

          The only difference now is that it has reached a state where multiple advanced users have given up on Xojo – and that caused others to stop and reconsider that maybe there is a problem after all.

          And as for Apple – they had an 18 month release cycle, and since they reduced that to 12 people complain that the quality is going down and a “Snow Leopard Release” is required. Figures.

          • RRM was good in theory but it didn’t meet our expectations or needs. It probably helped smooth out Xojo’s income though which is probably a bigger deal than they’d ever admit.

          • The proplem as I see it, is that Xojo Managment wants to attract newbie users (forget about the established customer base), And the only way to bait the trap for them is some “New and Shiny”… So Xojo is attempting to add new features and platforms while ignoring both existing product problems and existing paying customers.

            And as far as Apple is concerned…. With Xojo I am PAYING for a product, while macOS is FREE. So at least for me, there is a differnt level of expectations…. A level that in my opinion Xojo has failed to meet for a few years now.

          • What I meant, but obviously didnt say well, was that RRM assumed that Xojo _could_ rapidly fix bugs and also rapidly release well tested high quality new features.

            But the reality is has been something different.
            It has been “releasing rapidly” and quality has varied wildly over time.
            Going back to tick tock or one monolitihic release + bug fixes per year might serve them better and end up with “get the last release of every year as its ALWAYS the best” – which often used to be the case.

  2. This all seems like speculation at this point. When they put out the next release or they officially explain why the delay, then this conversation will have a context.

  3. I’d prefer an Intel tick tock model. Have four scheduled releases a year with the odd releases having new features (and a few critical bug fixes), and even releases with only bug fixes.

    Odd for new features would allow for that grand first release of the year to have the newest killer feature. Those of us that are more concerned about stability could then focus on the evens.

  4. Xojo doesn’t have the time for develop on 2020
    All time are set for closing threads on forum 🙂

  5. Even in our small shop we have a develop and a release branch allowing us to quickly fix bugs in the release branch and merge them back to develop. Are Xojo still using the binary format and cannot branch/merge the IDE?!?

    • no – they use text and SVN last I knew and I dount they’d ever go back to anything less

      But they also HAVE said “2020r1 will contain web 2.0” so shipping R1 without it would probably get them a lot of anger

  6. LOL, I came hunting this down becaus eI’m after a promised feature of R2020 and they just released R2019 3.2!!! DOH! That sucked! no MainWorker objects. That’s what I’m looking for right now. Threading to the rescue atm, but these workers look exactly like what I’m after

Comments are closed.