Redefine `MAINTAIN` label

[Chrimle]

Concept

• Assuming that a new feature is added, without affecting any existing features => RELEASE
• Assuming that a feature is removed, partially or completely => DECOM

Should MAINTAIN thus mean:

• deprecation
• refactoring
• non-functional changes
• bug fixes

Also, if any of these changes in actuality removes a feature, or makes it no longer default, then it is a DECOM.

Furthermore, perhaps there should be an emphasis on feature, functionality and behavior?

For example:

Fixing a bug, where the API previously returned X, when Y was expected, is INDEED a bug fix. Regardless of backwards-compatibility, it REMOVED/REPLACED the API which returned X, with a new feature returning Y. This is not considered MAINTAIN.
Furthermore, since this boils down to backwards-compatibility assessment, perhaps bug fixes such as this should not be solved by modifying the API, but instead add an OPTIONAL replacement API, deprecate the existing API, and eventually remove the bugged API? Then, the discussion about backwards-compatibility can just be thrown out!