Policy

This page serves as a repository of policy decisions taken that are relevant to the CloudVolume community.

There is no formal process at the moment for adopting resolutions, but if enough interest develops I'm open to it.

Semantic Versioning

Release numbering starting from Dec. 10, 2019 will follow Semantic Versioning interpreted as major.minor.micro (e.g. 1.0.0). All releases within a major version number should be compatible with each other and require no code changes by CloudVolume community members on release. Minor version increments indicate a new feature or redesign of a feature. A micro increment indicates a bug fix or a refactor. A performance increase can fall into a minor or micro increment depending on the intent of the update.

Adopted December 10, 2019

Master Must Pass Automated Testing

The master branch must pass automated testing, even prior to release of a new version on PyPI. If it fails, action should be taken as soon as practical to restore it.

Adopted December 10, 2019

Python 2.7 End-of-Life

Python 2.7's End of Life date is January, 1 2020. CloudVolume will support Python 2.7 up to that point. Numpy will be dropping support on January 1. We will monitor Python 2.7 usage on PyPI stats to see if it drops and revisit this in June 2020. As of March 2020, 2.7 usage was low but not insignificant. It was higher than Python 3.4 and 3.8 and similar to Python 3.5. https://pypistats.org/packages/cloud-volume

Adopted Feb. 11, 2019; Amended Dec. 10, 2019, March 16, 2020.