Software Firmware Update Suunto Vertical?!
-
@Mff73 So, essentially, it’s impossible
-
@avn3r90 Maybe reconsider…
From what I have heard being a field tester comes with a lot of responsibility. Yes, you get the latest firmware which solved some of the bugs, but potentially introduce new ones. I can imagine some of your activities get lost or corrupted because of the new firmware. But that’s life for a tester.If you value your activity and the data I would suggest you just stick to the production firmware. Maybe it’s not flawless, but it’s the best available.
@real_fieldtesters, please correct me if I’m wrong
-
@EzioAuditore Yeah, basically you got your device back without service being able to do something about it since the fixing update is not out. It made no sense for them to keep the watch while you could hold and use it at the same time.
So the result was to be expected.Now if you still have the watch, maybe you want to try and judge again next week…
-
@Egika said in Software Firmware Update Suunto Vertical?!:
Now if you still have the watch, maybe you want to try and judge again next week…
So it seems the date of the update is getting closer
I think it would be very valuable and would also calm some nerves if Suunto would at least announce an EDA for the update as soon as it can be reasonably reliably said.
I’m sure there will be people complaining again if the update is then delayed due to some unforeseen issue. But on the other hand, it would reassure a lot of other people.
Maybe someone can bring this up to Suunto.
-
@Stoke80 But this release will also/probably have isolated issues/particular use cases issues…so whatever the date it comes, some people will still be disappointed. That’s my guess.
And knowing the date of release will not change that… -
@avn3r90 Using a suunto watch!
(joking) -
@Tieutieu said in Software Firmware Update Suunto Vertical?!:
@Stoke80 But this release will also/probably have isolated issues/particular use cases issues…so whatever the date it comes, some people will still be disappointed. That’s my guess.
And knowing the date of release will not change that…I agree. But it would still reassure many people here in the forum who regularly ask for the update.
It would relieve the moderators, who have to answer the same question hundreds of times.
-
@Stoke80 I work in a software company. Announcing a « previsionnal period » for an update is ok.
But announcing a precise date long time ago is the best way to make people unhappy when it is finally delayed…
unless if it is really ready and validated !
-
@Tieutieu I guess people don’t need a precise date, but more than “soon”
-
@Tieutieu
… it’s agile style and that’s state of the art
it actually is more customer friendly but maybe difficult to understand -
@freeheeler If so then it’s a strange “agile style”.
One of the principles of the Agile Methodology is:
“Satisfy customers through early and continuous delivery of valuable work.”
In my company, devs team is using Agile Method. They deploy little pieces of software several times a week…
Suunto normally deploy one big piece of software, twice a year?
Garmin and Coros seem more Agile style than Suunto, isn’t it?
-
@jjpaz I think 2 big feature updates per year are good enough, even if we want new features on a monthly basis
But in between those bigger updates, multiple smaller bugfix releases would be great. I think this would vastly improve customer satisfactory. But I am sure Suunto knows all of this and there will be reasons why firmware updates don’t happen that often. -
@wmichi That’s the point. Software development must be agile to correct known bugs. New features is an optional add-on. Bug correction is a must.
-
@jjpaz Right. I am a web developer and I constantly create new releases for a website and lot’s of microservices. But I think wearables are a little bit different. There’s a lot more testing needed in the real world (what field testers do) and this takes time. So a strict agile approach maybe doesn’t work.
-
@Egika said in Software Firmware Update Suunto Vertical?!:
Now if you still have the watch, maybe you want to try and judge again next week…
-
@jjpaz
I’ve had 2 years in mind.
only because most sprints are 2-4 weeks doesn’t mean that they’re released in this pace.
what I wanted to say is: we DO have updates frequently and if necessary even very quick in case of significant issues.
the Race could as well be still unreleased under development -
Ultimately, it’s all about developer time and testing. It’s great to argue for commit early and often with firmware updates, but the reality is that you have to balance team time and you need to provide time for testing to ensure issues are fixed. There are no easy answers here. Been there.
-
@EzioAuditore sorry to see you go. I left Suunto a while ago for Polar. Works as expected, no mindlessly entering sleep times and getting wonky data, can zone lock on HR, get out of zone vibrations and navigation as normal and not as per Suunto logic. Hanging out here for fun and for my partner’s sake who still has her 9PP.
-
@wmichi said in Software Firmware Update Suunto Vertical?!:
@jjpaz Right. I am a web developer and I constantly create new releases for a website and lot’s of microservices. But I think wearables are a little bit different. There’s a lot more testing needed in the real world (what field testers do) and this takes time. So a strict agile approach maybe doesn’t work.
The bigger the software change the bigger the testing requirements.
I was working years ago as Quality Assurance testing engineer (in more critical projects than a sports watch) and it was easier test small pieces of software than a full software update with several features.
If you deploy a little software change is easier to test that isolated feature and to perform the regression tests to verify the old features are working fine.
If you deploy a whole new software update the testing requirements will be bigger and every little issue detected will create a new whole software update you must test again from beggining, until you meet the deadline and deploy the last “stable” software version (with “little” bugs not detected in the testing stage).
That’s the reason why the new watches seem “not finished” at the beggining. Development and testing resources and deadlines.Just my opinion, only Suunto knows what happens inside Suunto
-
@jjpaz said in Software Firmware Update Suunto Vertical?!:
ion, only Su
It was not my intention to raise a discussion about project management or software development
I just thought, that an estimated time would avoid several threads about the same topic and make live easier for the mods here in the forum.
However, I am waiting impatiently for the new software. But it can’t be long now.