Release Strategy

[flogu]

Hi, Am I understanding the release strategy correct - Updates are scheduled to be in the system before their is an update call for these changes? Is that on purpose and if yes.. why? I would expect an update call to inform the community beforehand.

Thanks in advance for your input and explanations,

Regards, Florian

[former_member86748 · Accepted solution]

Hello Florian,

We are not making any "Update Call" as you state as we do not expect any of our customers to have to change anything when we do a Release. Remember that all the changes we announce in our Release Announcements are nothing else than improvements to FSM - in other words, these changes are additive and do not disrupt the behaviour of the functionalities already running. Hope this gives you a better understanding. Note that this is common industry practice in SaaS.

Best

Sébastien

[flogu · Accepted solution]

... well . from that point of viw, yes it makes sense 🙂 Thanks for your answer! Will keep that in mind.

[VishnAndr · Accepted solution]

Which industry best practices are you referring to, Sebastian? I mean for example your colleagues from SAP Service Cloud are doing quarterly releases. With prerelease announcements and with separate upgrades of test tenants and productions tenants with 2 weeks difference. I remember there was the plan to align all SAP CX (I know that FSM is not CX anymore, but still the point is valid) products to the same strategy. The plan was announced 2 years ago or so. Nothing has changed ever since. Each product still does its own releases strategy without any consistency. So what has happened to the plan then?

Trusting SAP (or any other vendor tbh) that "upgrades", "updates", "improvements" would not break anything - meh, well, I know from my long experience with SAP and with more than 2 years experience with FSM that it's not the case. Things were broken. Things were changed without announcements. Intentionally or not - doesn't matter. As a result, I'm still wondering how SAP is managing all these different approaches on the release strategy in the cloud.

Coming back to the original question in this topic. At least, separating test and production tenants/companies would be much of an improvement. It would give customers and partners an ability to perform a regression testing at least. And adjust their solution.

Cheers,

Andrei