How to do software versioning based on Microsoft recommendations?

Asked

Viewed 113 times

0

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

Now the questions:

  • How each one works?
  • when should I implement a number bump? (e.g., when I make any changes to a file, when I fix something, etc...)
  • What is the advantage of using this type of versioning instead of semantics?
  • (optional) for what types of applications this version is recommended?

I don’t want to know the opinion of how you think it is versioned in this way, but how it should really be done and used according to what Microsoft recommends. I tried to search and search several times...search Google but I did not find, so I thought someone here could say!

versioning microsoft
  • 2

    I was not the one who denied, friend, but I think this answer should help: http://answall.com/a/114287/3635

  • 3

    Since the question is very specific I think only answers that can indicate a source will be valid. The question isn’t about how each one does it, it’s about how Microsoft does it. Otherwise it comes to mind.

  • @bigown is kind of like I don’t want to know the people’s opinion but really how to do it and use it according to how Microsoft recommends it. Well, I still don’t think I do it the right way. I tried to search and search several times...search Google but I did not find, so I thought someone here might know!

1 answer

0

Versioning is project specific, is defined by the team. It depends on the development objectives and methodology (the methodology influences the cycles, if the project has cycles). These things are open, there are several models but each team uses variations, creating their own. From officer only has the basic concepts (major, minor, build etc)

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

  • So you can.... Here you cannot debate on account of the bases in opinions, so there will never be a question about software versioning without only explanations of the meanings of words and their hierarchy....

  • It seems appropriate to me, because it is totally subjective. The rule itself is not so relevant, the important thing is to maintain consistency. But when we see the changes in the Mac OS and Firefox versioning scheme, we realize that even consistency isn’t so relevant either.

  • so you think you can do if it’s that kind of question?

  • 1

    Actually, I thought it appropriate can’t ask this kind of question here haha. Precisely because it is totally subjective.

Browser other questions tagged versioning microsoft

You are not signed in. Login or sign up in order to post.