search

nark / WiredClient

A Wired Client for Mac OS X
http://wired.read-write.fr
32 stars 9 forks source link

Consistent versioning #87

Open scisme opened 5 years ago

scisme commented 5 years ago

To avoid confusion we should have a consistent versioning and set CFBundleVersion to number of commits and CFBundleShortVersionString to the current tag, as described here:

https://www.mokacoding.com/blog/automatic-xcode-versioning-with-git/

nark commented 5 years ago

Ok, what I did from the repository side is:

  1. create tag when we want to release a binary (a Debug or real Release version)
  2. the tag is composed of version number + build number, as follow: 2.4-352
  3. then use GitHub Release feature to expose it to the world

You can see an exemple here: https://github.com/nark/WiredClient/releases

scisme commented 5 years ago

The point of using the script is to have a consistent build number that is derived from the number of commits from the git repo. 352 in this case is just a number you increase now and it doesn't really relate to anything?

So my suggestion is to just keep the tag as 2.4 and perhaps have one for the "real" release versions and the other could perhaps be together with some CI solution to have nightly builds like morris used to have?

So there could perhaps be a 2.4 (Release) tag and a 2.4.1 (Nigthly) tag.