Well in the post you were referring to, I was only pointing out that your wording was perhaps a little misleading - leading to other people commenting about lost updates - and that the part of the migration design that you were pointing to was a good one.
So I am not quite sure why you then end your post by saying that it is MY fault that you don’t prioritise safety in your design because I didn’t do early testing and give you early feedback? (A “blame the user” culture is never a good look IMO.)
Well, I wasn’t interested in testing, so I didn’t read that article. Instead I looked in the documentation section for details of the planned migration process and didn’t find anything. Indeed, this is the first time I have seen a link to this in all the discussions about app migration.
If I had read this at the time, then I almost certainly would have suggested that a pre-upgrade check for whether apps would migrate successfully or not was a necessity.
Those of us who have been around (or have worked in IT) - and are therefore somewhat cautious - will certainly worry about an upgrade breaking things & check the release notes before upgrading.
But those who are not particularly technical and who perhaps have done (much less risky) upgrades several times previously without any issues, might simply trust that the EE upgrade would be similarly issue free and just go ahead and do it, not realising that any TrueCharts apps they have will definitely stop working and that even iX apps might not work.
Even if they had read the Release Notes, they would still NOT have known that iX is still classifying 24.10.0 as suitable only for testers and not even suitable for Early Adopters.
So, can we all please start to have a little more empathy for non-technical users who trust iX to ensure their systems won’t break when they upgrade to a new version and who suddenly find their apps broken and don’t personally have the technical skills to diagnose and fix it.
This gave me quite the laugh this morning. I think folks here need to take a deep breath, maybe go out and touch some grass periodically
The software status page you refer to lags behind releases, we only update it every couple weeks at most. The release came out just a couple days ago and we won’t likely touch the software status page again until late next week.
Based on the update rate of the software (2x Dragonfish, 4X Cobia, and 10X 13 CORE) vs to the number of bugs being reported (and the severity) we can easily recommend this now for general usage. If you want to compare back to CORE days, this would be around the equivalent of a -U5 release in terms of adoption to bugs ratio, yes we’ve come that far in a few short years. Anybody who wants to paint some negative picture of how this is a regression in quality of SCALE vs CORE is just flat out misrepresenting history. I was there, and better yet, have the releases and bug notes to back it up. There was a reason most folks waited until a -U3 or even -U4 to update back in 11, 12 or even 13 days. Not so now.
I might also add nobody is forcing an update to a brand new .0 on anybody. There is no auto-updating tool. Lots of folks purposefully wait until a .1 or .2 release, which is perfectly reasonable to do if you choose.
Anyway, thanks to everybody updating and providing useful feedback on issues we should investigate! We super appreciate it as always and please keep those coming so we can review and get any necessary fixes into the .1 in a few weeks time.
