c# - Program version -


this question has answer here:

what i'm asking maybe little weird there rule in changing .net program version when you're adding new features?

to more clear:

  • you have initial c# program , add few new features it.
  • your initial version 1.0.0.0, update 1.1.0.0

is how works? or has how bigger change?

example:

  1. changed whole ui design (v1.0.0.0 updates v1.1.0.0)
  2. fixed little bug (v1.0.0.0 updates v1.0.0.1)

any answer welcome!!

use semantic versioning:

given version number major.minor.patch, increment the:

  1. major version when make incompatible api changes,
  2. minor version when add functionality in backwards-compatible manner, ,
  3. patch version when make backwards-compatible bug fixes.

additional labels pre-release , build metadata available extensions major.minor.patch format.

see http://semver.org/ more details.

in terms of ui it's little more gray. argue wholesale changes interface should classed major adding or tweaking few layouts classed minor.


Comments

Popular posts from this blog

resizing Telegram inline keyboard -

command line - How can a Python program background itself? -

php - "cURL error 28: Resolving timed out" on Wordpress on Azure App Service on Linux -