The fact that they stopped the roll at 20% and it didn't update toady may indicate that there was an issue with some of those first 20% users. I wouldn't get into too much of a hurry to receive these updates. Being somewhere other than the first 20% means that you are unlikely to get something that results in boot loops.
Why STOP and only 20% Software Version 4.00 Phased Roll Out?
It's quite common to do phased rollouts like this, and I assume the few extra days we've seen before moving forward this time is simply due to the weekend. Unless they've encountered any major issues with the first 20% of users my best guess is that we'll see the continued rollout as soon as the Garmin people get to work in the US later today.
If you swim, don't hold your breath for this update. There is no change to the complete mess that the updated OWS (no GPS measurement for distance) and, for the first time today, I started getting strange results in a pool swim. I maintain that Garmin should be telling us what is wrong with the swim portion and of the update and what they are doing to fix it. I have had to resort to an old 920XT that has not been updated to get an accurate measurement
It's quite common to do phased rollouts like this, and I assume the few extra days we've seen before moving forward this time is simply due to the weekend. Unless they've encountered any major issues with the first 20% of users my best guess is that we'll see the continued rollout as soon as the Garmin people get to work in the US later today.
All of this is only my speculations of course.
Yep. Totally agree, this is Standard Operating Procedure for Garmin roll-outs. Obvious people are anxious to get it :) ... I only have one issue I hope is resolved (Elevation issues during activity). So far really loving my 5x Plus
No, it is not SOP. If they stop a roll, it is generally because there is an issue with the software install.
Ok buddy. I am a software release manager for a large healthcare provider and we do this all the time. This is SOP, if they detected a problem, halting is also SOP. That's the entire point of this exercise. Additionally for larger shops it provide an opportunity to manage back-end DB and API performance/load along with reducing load on distribution infrastructure. All of the issues do not have to be device side... For example during the new update all Fenix watches start re-syncing and expensive (In terms of CPU load). health or fitness metric metric
I appreciate this deployment methodology, although I want the update like everyone else, I prefer it to be right :)
No, it is not SOP. If they stop a roll, it is generally because there is an issue with the software install.
Fair enough. So you are saying something similar... We have no idea what the time frame Garmin internally had expected for the roll out. They may have very well intended to reach a 20% milestone on Friday and monitor database performance over the weekend, or any other number of infrastructure health metrics :)
My point is this does not have to be a client side issue to cause the perceived delay, it could be a non-issue altogether.
