All,We need a convention to assign a version number for our product. After I research. I found this post answer my question. And it lead me to the http://semver.org/, The Semantic Versioning Specification.I think almost everything in the Semantic Versioning make sense to me .But only one thing I didn't understand . In the Semantic Versioning Specification Rule No1. Please help to review it .Software using Semantic Versioning MUST declare a public API.I can't understand what does public API mean.In our products. We have all kinds of format software. like executable program, library, web site etc. Some of them without public API, like executable program. IMO, I think the Public API means some public methods or functions which can be referenced and called by other software. like Fo-Dicom which is a Class Library, can be referenced by another project. Without Graphic UI. Just provide a group of API to deal with DICOM file based on the .Net Framework. So My question is what exactly the Public API mean in the Semantic Versioning?What kind of products are not suitable for Semantic Versioning? Thanks.
What does it mean Public API in the Semantic Versioning Specification
project management;version control;versioning