BraamCLSA Member since 2012 100 posts
Posted: February 18, 2016
Last activity: October 4, 2018

Any differences between committed and uncommitted hotfixes?

This seems like a dumb question, but I'll ask anyway... Since we got to a point where Hotfixes could be rolled back, I'm wondering what the value is in actually committing a hotfix?

Does an uncommitted hotfix behave 100% the same as a committed hotfix? Does this include code changes? I'm presuming it does, and therefore, what is the value for me to go from a state where I can back it out (uncommitted) to one where I can't back it out (committed)?

Anyone who's had a bad experience with Hotfixes in the past will attest that one of the factors is the lack of any regression test plan provided with them. There's never any supporting material that suggests what I should check to see hasn't been impacted by the hotfix. As a result, at what point am I ever satisfied that the hotfix has not introduced a regression that I simply haven't stumbled across yet? Answer: never.

So why would I commit hotfixes if leaving them uncommitted gives me the same functional outcome whilst leaving the door open to back out a hotfix subsequently found to be destructive.

***Edited by Moderator Marissa to update categories***

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Low-Code App Development Installation and Deployment
Moderation Team has archived post
Share this page LinkedIn