Best Practice: Software Versioning [closed]

by

You should start with version 1, unless you know that the first version you “release” is incomplete in some way.

As to how you increment the versions, that’s up to you, but use the major, minor, build numbering as a guide.

It’s not necessary to have every version you commit to source control as another version – you’ll soon have a very large version number indeed. You only need to increment the version number (in some way) when you release a new version to the outside world.

So If you make a major change move from version 1.0.0.0 to version 2.0.0.0 (you changed from WinForms to WPF for example). If you make a smaller change move from 1.0.0.0 to 1.1.0.0 (you added support for png files). If you make a minor change then go from 1.0.0.0 to 1.0.1.0 (you fixed some bugs).

If you really want to get detailed use the final number as the build number which would increment for every checkin/commit (but I think that’s going too far).

More Related Contents:

  1. Definition of “downstream” and “upstream”
  2. Homebrew install specific version of formula?
  3. Best practices for API versioning? [closed]
  4. How can I force clients to refresh JavaScript files?
  5. How to compare two strings in dot separated version format in Bash?
  6. How to have an auto incrementing version number (Visual Studio)? [duplicate]
  7. How do you compare two version Strings in Java?
  8. A definitive guide to API-breaking changes in .NET
  9. How to version control a record in a database [closed]
  10. How do I set the version information for an existing .exe, .dll?
  11. How to mark a method as obsolete or deprecated?
  12. How to allow users to check for the latest app version from inside the app?
  13. Git and the Umlaut problem on Mac OS X
  14. How to perform better document version control on Excel files and SQL schema files
  15. A regex for version number parsing
  16. Temporarily put away uncommitted changes in Subversion (a la “git-stash”)
  17. Maven versioning best practices [closed]
  18. How do you use multiple versions of the same R package?
  19. What are the best practices for versioning XML schemas?
  20. ASP.NET MVC security patch to version 3.0.0.1 breaks build [duplicate]
  21. Setting the version number for .NET Core projects – CSPROJ – not JSON projects
  22. Versioning Database Persisted Objects, How would you? [closed]
  23. How to use JSF versioning for resources in jar
  24. Skip composer PHP requirement
  25. API Versioning for Rails Routes
  26. How can I auto increment the C# assembly version via our CI platform (Hudson)?
  27. How do I sync the SVN revision number with my ASP.NET web site?
  28. ASP.NET – show application build date/info at the bottom of the screen
  29. nuget spec dependencies, get latest version?
  30. Database – Data Versioning [closed]

Leave a Comment