Best Practice: Software Versioning
Posted
by Sebi
on Stack Overflow
See other posts from Stack Overflow
or by Sebi
Published on 2010-05-19T09:58:42Z
Indexed on
2010/05/19
10:00 UTC
Read the original article
Hit count: 252
versioning
|best-practices
I couldn't find a similar question here on SO, but if you find one please link.
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 should'nt any commit to a version control system be another version? or is this only for versions which are used in a productive manner?
© Stack Overflow or respective owner