I graduated in 1990 in Electrical Engineering and since then I have been in university, doing research in the field of DSP. To me programming is more a tool than a job.
We look at major versions for the Release Radar as we want to highlight breaking changes and new features, as opposed to backward compatibility or bug fixes.
However, one can introduce an important new feature without breaking backward compatibility.
Say I have an open source ML library with some API to be called by your application. I could add a new ML model without breaking backward compatibility. You can use the new library with old code without any problem. Therefore, the new version number will update the minor version, not the major.
Nevertheless, the addition of the new ML model can be an important improvement.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
However, one can introduce an important new feature without breaking backward compatibility.
Say I have an open source ML library with some API to be called by your application. I could add a new ML model without breaking backward compatibility. You can use the new library with old code without any problem. Therefore, the new version number will update the minor version, not the major.
Nevertheless, the addition of the new ML model can be an important improvement.