Description
So we had this discussion in our team that fix should basically only be used when there is a bug ticket. And because of that most people tend to use chore for everything except features and refactor, because
chore implies it's not a bug and low impact.
However, i think that anything that changes a feature in production should be regarded as a fix. And the reasoning behind it is that, even if it was the stakeholder that changed the specification, your application is no longer following the specification for this feature. Thus, you should make a fix for that.
Work-arounds for bugs in other systems, might also be a fix.
My take is that chore should only be used for configuration changes, adding stubs, new classes that are not yet in use , updating readme etc. Things that do not effect production in any way,
But i don't know. What do you think? What is the intention of fix? Do you think the intention is clear in the current document?