I recently thought on how i'd go about versioning a game I'd create. Certain questions came to mind:
Should I start with ^1.0.0 or ^0.1.0? How would I go about incrementing the version?Then I came across
Semantic Versioning 2.0.0 which gave me a lengthy and detailed description on how I should go about game versioning. So I thought I'd share.
Here's a short summary of
Semantic Versioning 2.0.0 with a FAQ on initial development:
Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.
FAQ: How should I deal with revisions in the 0.y.z initial development phase?The simplest thing to do is start your initial development release at 0.1.0 and then increment the minor version for each subsequent release.
Then I came across Semantic Versioning 2.0.0 which gave me a lengthy and detailed description on how I should go about game versioning. So I thought I'd share.
Here's a short summary of Semantic Versioning 2.0.0 with a FAQ on initial development:
Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.
FAQ:
How should I deal with revisions in the 0.y.z initial development phase?
The simplest thing to do is start your initial development release at 0.1.0 and then increment the minor version for each subsequent release.
Cheers,
Dubious Game Studios