1

I'm preparing to open source an XCode project I've been working on privately, on Github.

I am planning on using Github's release feature and and tag the initial release as 0.1.0. This much I know.

But I have one question: What's the best practice for the version number and build id of the XCode project itself going forward?

  1. Do I need to update the version/build-id every time raise a version on Github?
  2. Should these numbers be synchronized?

closed as primarily opinion-based by curiousdannii, Mureinik, ArtOfCode Nov 3 '16 at 18:50

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.

  • What? Why did this get a down vote without explanation? That's just sad :( I think this is a good question, and definitely deserves an up vote around here. – Zizouz212 Oct 28 '16 at 0:47
  • This is strictly an opinion based question, though a large consensus would say to just use semver, and I'd agree! But what do you mean by "raise a version on Github"?? – curiousdannii Oct 29 '16 at 13:41
  • @curiousdannii you can specify version and build id on XCode projects. I was wondering if this should be in sync with the version I use on Github. The former is for shipping a product. You are required to raise versions everytime you re-submit to the appstore. On the other hand, the latter is more for milestone purpose. I wasn't sure what the best practice was for dealing with both. – Vlad Nov 12 '16 at 14:39