so, about that major update
 

The major update was pushed back when it was realized there was an issue in the updater (if I understood correctly).

Ok.

I thought the issue was resolved and we would see the update pushed soon after.

Any ETA on this major update? (whatever it is)

soon™

I wonder if they are holding off to ensure that more of their customer base has installed the recent updates that allow the major update. I would like to think, however, that it would be smart enough to know that the user was trying to "skip" and update and force them to install the necessary fix before allowing the user to download and install the major update.

The issue is a bug in the logic that detects that a new version is available that is required and necessitates a tightly coordinated update with the server. The bug in the CLIENT, and it will cause things to fail in obscure and confusing ways. That means that whenever we release the major update, anyone who has not yet updated to the interim release will encounter the same issue. There is nothing we can do to retroactively fix the version that users have running on their computers today, and that's the rub. The best we can do is fix the bug within the interim updates and get as many users as possible to install those updates before we release the major update.

So we are waiting until a meaningful percentage of users have updated to the interim releases so that they will not encounter this bug.

So we're waiting for enough average users to update?

Dear Heavens, we're doomed! ;-)

Thanks for the answer. I don't suppose you could make the wait easier by telling us what's in the update? *wink*

How are you collecting this metric? is it by installed base or by recent login? You do know that some significant percentage of any user base will have installed a software package and stopped using it right?

It seems some of you have a very low opinion of our ability to consider these factors. Yes, we are taking these factors into consideration. I'm not going to go into all sorts of silly details that will just be a distraction from continuing development on everything that's still in the works.

I realize that it's now football season, so armchair quarterbacking is all the rage, but come on, folks.

Yes, I realize that was a little snarky, but I interpret the above comment as questioning our basic intelligence and experience. So I'm honestly a bit offended. At least @Seregil put a smiley face after his comment, so I'm going to assume he wasn't serious.

You'll note that I said MEANINGFUL. That's a heck of a lot different than "majority", "large", etc. It means we're taking all the various factors into consideration and identifying a target that makes sense. Sheesh!

That was done at the bottom of the announcement that the release was delayed, which was also included in the monthly newsletter. Please refer there for a glimpse of some of the enhancements that will be in the upcoming release.

You must have been waiting for me... I have upgraded to release 200... so let's do the big one!



j/k :)

Oh, I saw it. I just get the feeling there's more to it than is hinted at. Mind you, that's probably wishful thinking on my part.

I'm desperate for the Web client which requires the content market which...

Anyways, keep up the good work, I was just curious about when the mentionned big update was going to go live. :)