How to set the software version?

33

I would like to know what software version number (s) are and how they work, such as v1.1.2 what does it mean? Is there any standard or recommendation for web application versions?

    
asked by Lucas Fontes Gaspareto 03.12.2015 в 22:52
source

3 answers

34
  

I would like to know what software version number (s) are and how they work, such as v1.1.2 what does it mean?

According to Semantic Versioning :

  • The first number indicates that the system has changes that make it incompatible with previous versions;
  • The second number indicates that the system has changes compatible with previous versions, within the first number;
  • The third number indicates that the system has minor changes, such as bug fixes and features that do not impair backwards compatibility.

Optionally, a fourth number, called a release, is defined. Indicates the current build number of that code, within a scope of modifications.

  

Is there any standard or recommendation for web application versions?

Semantic versioning can be used. Some other systems use a versioning number formed by the release date. This is adopted when the modifications are frequent (not to say daily) and that it is not worth taking into account a semantic approach.

Examples:

  • Ano.Mes.Dia.Build ;
  • Ano.Mes.Dia.Estado . State can be Alpha , Beta , dev , stable , etc.;
  • Ano.Mes.Major.Minor.Fix (can also have status or release at the end);

Each team ends up inventing its format. These are some I have seen and used.

    
answered by 03.12.2015 / 23:04
source
10

There is no pattern. Each project adopts what suits you best. Then the explanation of what each number (if numbers are used) means should be provided by the project itself.

What is recommended is semantic versioning. Even by setting some rules, they are subjective. This has already been answered in another question (I will not repeat here what has been answered before).

And there's a question in Programmers with some possible standards to adopt . It has my "answers" there and several other examples as you can use creativity and you can not rely on intuition to determine what the numbers represent.

    
answered by 03.12.2015 в 23:01
4

Generally each company defines its versioning methodology. A very common standard used in the market is the following: VERSION. RELEASE. REVIEW

VERSION: You add a VERSION number if the project is an evolution.

RELEASE: A RELEASE number is added if the project is an improvement (eg exclusion or inclusion of new features).

REVIEW: Added a REVISION number if the project is a fix of existing functionality.

    
answered by 15.03.2016 в 14:54