There is an optional update available but it is recommended you do update when you can
Does this optionally make us yield more watts?
Itâd be helpful if they displayed release notes when notifying about an update. Itâs hard to know if itâs worth updating or not if you donât know whatâs changed!
Haha, yes, especially if itâs even labelled as optional.
What has changed that itâs not essential and how am I supposed to know if I want to take the option if I donât know what the option even is?
Itâs optional as opposed to forced, which means that you donât have to do it before your next activity. Forced updates have caught those out in the past that join an Event or Race too late to be able to complete the update before the ride starts.
Saying itâs optional removes the concern about that happening so that the update can be done in your own time.
The Wahoo updates page hasnât shown the change log and so I had to go to the iOS App Store to get this:
Just for clarity, then, this should be listed as âdeferrableâ, not optional, if what is meant is that it doesnât have to be applied now but it will be applied in future and that would at least remove one of the questions
Yes @Jon .
Iâve never come across an update that isnât either giving added features or fixing any bugs, so they are always worth applying. The âoptionalâ wording is perhaps misleading, but as I said is perhaps more to do with calming the nerves of those that have experienced Forced updates in the past preventing them from riding. I guess long term users understand that context, but itâs lost on those new to the platform
I suppose that âwe recommend you do this when you canâ is different to saying, âyou donât need to do it at allâ. If the release notes were linked to it would certainly make things clearer!
Iâve worked in IT Management for more than 22 years and spent 10 of those working for a software development company.
Within the IT sphere it is a fairly common position of âDo I need the fixes in this updateâ or you donât update something that is already working.
Anecdotally, for amusement, I know of someone who bricked a data center UPS while applying a patch recently, when he called the UPS provider for support their first question was âWas the UPS working correctly beforehandâ and upon his reply in the affirmative the second question was âWhy were you patching it thenâ
Of course software updates are almost always meant to add nice features or fix bugs, but it is also often the case, as is the nature with software development, that fixing one bug can sometimes cause another. Weâve all been through patch rollbacks.
Thatâs why I suggested the term deferrable, because âoptionalâ (especially without patch notes) implies things like âTexture pack for AMD graphics cardsâ as opposed to âhelpful bug fixes, but you donât have to apply it now if youâd rather rideâ, thatâs all
Likewise I have a 40 year background in Industrial Process Control & Measuring Systems, working with hazardous and explosive chemicals. I used to specâ embedded systems for our thickness scanners that used a radiation source simply because of the dreaded updates on OS/2 and Windows
âIf it aint broke donât fix itâ is a very wise philosophy!!!
Letâs hope that someone involved with the wording of update notifications reads some of this