Best Practice: Software Versioning [closed]

Is there any guideline or standard best practice how to version a software you develop in your spare time for fun, but nevertheless will be used by some people? I think it’s necessary to version such software so that you know about with version one is talking about (e.g. for bug fixing, support, and so on).

But where do I start the versioning? 0.0.0? or 0.0? And then how to I increment the numbers? major release.minor change? and shouldn’t any commit to a version control system be another version? or is this only for versions which are used in a productive manner?

12 Answers
12

Leave a Comment