4 ms·
The requirement of a public API seems weird to me. What is the point of that; why should my versioning scheme meddle with whether I want to release an API? Als
by lucb1e 10y ago
The requirement of a public API seems weird to me. What is the point of that; why should my versioning scheme meddle with whether I want to release an API?
Also a small note on the name, I don't see how `4.7944+beta7` is "MonoVer/MVer/MoVer" since it's not quite... mono (http://www.dictionary.com/browse/mono- http://www.dictionary.com/browse/mono-). It has between two and three components.
- sephlietz 10y agoThe "mono" this is referring to is "monotonic", specifically "monotically increasing" (https://en.wikipedia.org/wiki/Monotonic_function https://en.wikipedia.org/wiki/Monotonic_function). That is, when layed out chronologically the components of the version numbers are always increasing.
- solipsism 10y agoTechnically, "never decreasing" is more correct than "always increasing", regarding "monotonically increasing". In MonoVer the Compatibility number is monotonically increasing but not always increasing. The release number is both.
- ajanuary 10y agoWithout a defined public API, you don't have any way of determining if a change is breaking or not, and hence you don't know when you should bump the compatibility number.
- solipsism 10y agoPublic doesn't necessarily mean "outside my company" or "seen by anyone but you". It refers to the interface available to users (human, if it's an application, or other packages, if it's a library). If it doesn't have a public API it's not usable by anyone and you can save time by not working on it anymore.