How to do software versioning based on Microsoft recommendations?

0

I've seen a lot about the semantic versioning: Major, Minor and Patch . But something very curious is the versioning of software recommended by Microsoft: Major, Minor, Build, Revision .

Now the questions:

  • How does each one work?
  • When should I implement an increase in number? (eg when you make any modifications to a file, fix something, etc ...)
  • What is the advantage of using this kind of versioning instead of the semantic one?
  • (optional) For what types of applications is this versioning recommended?

I do not want to know the opinion of how you think you are versioning this way, but how you really should do it and use it as Microsoft recommends. I tried searching and searching several times ... but I did not find Google, so I thought someone here could tell!

    
asked by anonymous 06.04.2016 / 23:53

1 answer

0

The versioning is specific to each project, it is defined by the team. It depends on the objectives and the methodology of development (the methodology influences the cycles, if the project has cycles). These things are open, there are several models but each team often uses variations, creating their own. official only have the basics (major, minor, build etc)

I do not think it makes sense to have a Microsoft recommendation because of this.

    
07.04.2016 / 03:20