search

mediamonks / frontend-coding-standards

Media.Monks - Frontend Coding Standards
60 stars 23 forks source link

We should not use the name "bugfix", because this indicates that there was a bug. And we do not make bugs :-) #72

Closed ThijsTyZ closed 1 year ago

ThijsTyZ commented 3 years ago

We should not use the name "bugfix", because this indicates that there was a bug. And we do not make bugs :-)

Better call this just fix

_Originally posted by @ThijsTyZ in https://github.com/mediamonks/frontend-coding-standards/pull/69#discussion_r588338930_

leroykorterink commented 1 year ago

A bugfix and hotfix are not the same. Use the bugfix prefix when you're following the normal release schedule in a project, use the hotfix prefix for problems that need to be deployed ASAP and need resolved in the main branch.

We should probably add that explanation to the README 😉.

ThaNarie commented 1 year ago

Naming something fix means it was broken, so it doesn't really make a difference if you call something bugfix or fix. A bug doesn't imply reason (i.e. human error), it could very well be introduced by an external reason, it just means it was broken, and it needs fixing.

So I'm closing this issue, unless someone comes with a convincing reason to change the name – if we even keep it altogether, since IMO bugfixes are technically the same as features, so might not even need a different branching prefix.