Hacker News new | ask | show | jobs
by xmprt 1486 days ago
My understanding is that initially they have version 1.4.2 and release 1.4.2. Then in the next commit, immediately after release, they bump the version to 1.4.3.alpha0 or something of that nature.

I personally think that's messy because it requires two changes to the version instead of one and there's no way of knowing that the next version will be 1.4.3. If a developer makes a breaking change, will they update the version in the code to 2.0.0.alpha0 or do they fix the version when they release?

I suppose if you have nightly releases then it could make sense but then I think using the date or the commit hash as the version number would make more sense.