Why do you announce a big update but do not deliver it to your subscribers?
Try reading the release notes one more time and you will see that this release will roll out to everyone, but not at the same time. So be patient
Gert, thank you for your answer and for your advice. I have read the announcement and have understood what there is said.
What I am wondering is why after five days there is no update here or at least a clarification that problems occured after partly rolled out.
Demanding this is not too much, I think. We are paying subscribers and Roon is not a free software.
I don’t know their staging schedule but staging over 5 days isn’t unusual. So in this case, the bulk of users would get it on day 5. But if they are staging over, say, 7 days, then most people would get it on day 7. (It’s also possible that they skip weekends to avoid issues occurring for people over the weekend when they have time more music and support is not available. In this case, it would obviously add more days until everyone has it).
Ramping up slowly is the point of the whole exercise, but it might help if the release announcement told us what to expect to avoid confusion. (Edit: Oh it does)
You might want to re-read the announcement. Your understanding / expectation does not match what’s clearly stated in the release notes… in bold…in the first paragraph. Hard to miss if you ask me.
The announcement was last week. Based on the above, it should be made available to all users by the end of this week.
The whole point of this type of release approach, which everybody from Google to Facebook also does, is to watch and learn before destroying too many people’s experiences. In the case of Google and Facebook, these deployments actually take several months to reach everybody. What Roon Labs knows you are paying for is quality software, not just sloppy new releases all the time. They are in a transition now, and it’s difficult for all of us to adapt to new things, but that is the point, and after quite some time when this becomes the standard, everybody will just expect it, and it will not seem so odd.
I always like to imagine that I don’t have a release because the authors found issues in the earlier deployments, and they are saving me from those issues, which may be worse than the issues I already have.
Trying to understand the psychology of all this.
If Roon works as described, what is the issue?
If you didn’t know about the update, you’d be much happier, i reckon.
Was recently reading about the Neuroscience of Fairness and Injustice… maybe because the update appears random, that there’s an assumption that whoever got it before me is more worthy, or better, or something. “I’m a lifetime subscriber, and I haven’t gotten the update yet. And this rando over here who’s running a trial subscription already has the shiny new version! It’s not fair.”
Life has an element of randomness that we all experience, and we just need to find happiness and grace and contentment in that. Sometimes we benefit. Sometimes we are harmed. Sometimes it’s someone else.
Ahdunno.
I received separate notifications this morning for updates.
First one was for my Windows laptop and that installed without any issues.
Then I received the notification for The NUC/ROCK which also installed without any issues.
Both are now on 1353.
Just got the update.
Also here in France, 1353 was rolled out. No major glitches.
I just rebooted my Roon Core and got the update straight away…
The problem is that all my iOS apps have updated but my ROCK and Windows controllers have not. This is going to break something at some point…
I was thinking the same. There have been updates in the past where both server and remote needed to be updated at the same time to work correctly.
PS - no update here (US) yet, though I’m in no hurry since there’s nothing in the update I urgently need.
I don’t see that it has to. Surely the latest remote can be made compatible with the penultimate server. It has to anyway, because e.g. the ROCK installer is never the latest version.
And from now on Roon will have to make sure that this isn’t the case, but that’s surely doable.
These guys are smart. They won’t stumble into version incompatibility issues.
In software parlance, the relevant terms are “forwards compatibility” and “backwards compatibility” - and which term applies to which scenario is, as in many things, mostly a matter of perspective
In this case, they need the client apps to be backwards compatible. The client apps need to understand, and adapt, to the version of the server they’re interacting with. This is more complex than what they were doing before, but it’s a good thing for Roon to do.
I would personally like to seem them extend this version tolerance to how they think about Early Access. Currently, Early Access is an all or nothing option in which an Early Access server can only be used with Early Access clients. If they were to allow production clients to talk to Early Access servers, I’d give it a shot because it would allow me to do it without forcing my family to go through the iOS gymnastics involved in early release.
@LarryMagoo - a reboot didn’t result in me getting the update. I suspect that your user account fell into the update ring and that it wasn’t your reboot that caused you to get it. Just a guess, though.
Well I hope you’re right. I have experienced issues of the this nature in the past with Roon. Using it since 2017 when it was pretty solid, is in contrast to Roon of today in which quality and stability have taken a significant nosedive IMO. Maybe this new release approach will improve things again, I guess we’ll see.
Just downloaded build 1353 to my windows 11 pc and everything went smooth
Still waiting for the update to show up in Linux Roon server…
Me too. Smooth.