Versioning and Workflow - skytreader/PyGame-Objects GitHub Wiki

Follow semver. Version is defined in components/__init__.py as well as setup.py.

Milestone1, as tagged, should be considered version 0.1.0.

We are skipping straight to minor version 0.3.0 because between Milestone1 and today, a lot of functionality has been added without being properly noted in version numbers.

Patches and minor versions (whichever needs updating) will be updated weekly. Again, they will only be updated, if and only if changes which merit that update were pushed within the week.

In the development branch, the current version string will have a "-dev" suffix. This suffix will be removed upon the release of a new version, with the appropriate version bumps. This means that version x.y.z-dev is the development version after the release of version x.y.z.

Missing tests/coverage are considered bugs.

New features do not increment the minor version until complete. So long as it is a work in progress it can only increment the patch version.

Lastly, for purposes of personal superstition, the version string components will skip numbers which follow the regex pattern 5+. :stuck_out_tongue_winking_eye:

See also: commit 1b1c9adb11b2e5dba5032379c6b1e93b93d1cf68

Docker images

Docker images are available at skytreader/pygame-objects. The latest version is tagged as latest and every release version will also be tagged appropriately. The experimental version is highly unstable and come with no guarantees.

Docker images are updated as soon as the corresponding version is pushed to master.