Me neither on the Winders side. I guess Epicor made the jump from telling us ātesting on this release is requiredā or not to āyou donāt get the optionā
Funny enough, I was told that the fix for one of our PRB tickets was targeted for 2025.2.14 with an ETA of 3/6/26. I had assumed, though, that the availability date would apply only to Pilot or be offered as an optional upgrade.
Doesnāt help we are all on edge these days with all the other things going wrong. I had to go take a quick walk around the shop after this one. Might need to start therapy
I suspect the same, somebody probably pushed something out wrong. On a seperate note I think Tim needs his own signal of him in his helmet like his profile pic.
Kinetic - Americas on cadence customers are scheduled for the 2025.2.14 Pilot update:
From: Wednesday, March 4, 7:00 PM Local Datacenter Time
To: Thursday, March 5, 5:00 AM Local Datacenter Time
Your Pilot system will be unavailable for several hours during this time.
An all-clear message will be posted. Testing is optional.
Note: The update does not apply to Flex Option customers who have deferred their upgrade.
I got a set of these for every region, too. We get.. Thursday and Friday to test! At least we went from inability to test to ātesting is optionalā. What a roller coaster
About the 2025.2.14 Upgrade Announcement, Letās Reset the Sequence
Alright⦠this oneās on us.
We communicated the 2025.2.14 production upgrade before Pilot was available. Thatās backwards. I completely understand why that raised eyebrows, especially for those of you who want to validate changes in Pilot before anything touches Production.
To be clear, we do not push to Production without going through Pilot. The release process was correct. The communication order was not. That sequencing error created unnecessary concern, and thatās on us.
Pilot communication is being posted, and we are correcting the rollout messaging so it reflects the proper progression.
2025.2.14 contains important fixes related to the Linux migration work. We moved quickly because those fixes matter, but moving quickly does not mean skipping steps in how we communicate. We should have ensured Pilot visibility first, then sent Production communication.
Consider this the reset⦠fire extinguisher has been deployed.
Self-Managed Customers
Since there is an upcoming migration to the Linux platform, we strongly recommend that self-managed customers apply 2025.2.14 in advance of that transition.
Having this update in place before the migration will help avoid compatibility issues and support a smoother cutover.
More detailed guidance will be published shortly so expectations and timing are clear.
Appreciate the fast feedback. You were right to question the sequence. Weāre correcting it and tightening up how these announcements go out going forward.
Are there any significant changes in this release other than emergency fixes? Pilot and Prod are back to back according to the latest email. No time to test much if at all.
OK, so what EXACTLY is this upgrade going to contain?
ONLY related to Linux, or anything else?
And, if related to Linux, is there any impact to Users?
Is it even worth spending 2 days testing in Pilot when it seems like Epicor just deploy whatever they want into Production, or canāt explain why the 2 environments react differently if Iām giving them the benefit of doubtā¦?
Weāve been on Kinetic for 9 months and been through 2 āupgradesāā¦Both have been complete disasters for us!!
I am wondering too who is going to answer all our questions. We get information from Tim but is there anyone at the top that we can voice our concerns to? I know this is one upgrade no one is feeling confident about.