Our Prod got 2025.1.8 and the hot fix over the weekend but Pilot wasn’t patched yet.
1 Like
We’re new and not yet live so forgive my ignorance.
All things considered, I trust it made sense to roll out a hotfix to prod in this case (vs what? delay normal cadence?) but putting aside whether this should’ve been caught in QA before release, does this not speak to the tightness of normal customer testing timelines? I mean, look at the abnormal push behind the scenes it took to make this happen. I’m sure I’d be grateful if we were live but is this normal procedure?
did on-cadence customers have an opportunity to delay between discovery and prod release?
Can’t imagine what would happen if the breaking change was, rather than one affecting ALL customers, some obscure but critical feature like say AUOM where we are in a small minority affected but dead in the water just the same. Some issues take weeks just to get support to repeat and escalate let alone prioritize, fix, release. what then?
It shoudln’t be normal procedure but unfortuantely this isn’t the first time this has happened in a dot release.
2 Likes
It happens enough (we are on-prem) that we are always a number of releases behind just to make sure nothing breaks (especially in our customizations)… honestly it has been a crapshoot since the push to Kinetic… I will only state, that it is getting better, but this particular bug was a big (and obvious) miss.
1 Like
As mentioned it’s not “normal” but it’s happened often enough that our C-suite is considering going back “on-prem”.
4 Likes
Is that even possible? We’re headed to the cloud in the fall - uplift is in progress.
1 Like
No idea but they’ve asked our IT director to inquire about it.
OK thanks…hopefully we don’t run into that scenario but always good to know one’s options
You can, but buying out the cloud contract is a very expensive proposition.
1 Like
Aha…good to know. Hopefully things go well for us in the cloud…we’re fairly vanilla build-wise, save for some EDI-related items. Cautiously optimistic.
1 Like