git clone git@github.com:magento/magento-semver.gitcd magento-semvercomposer install
php bin/svc --help
php bin/svc compare- Compare a set of files to determine what semantic versioning change needs to be done.php bin/svc update-breaking-changes- Update the file with a list of backward incompatible changes between two sources.
- Magento-semver development should happen against the
developbranch. - New releases will shipped monthly. However, new releases will only occur if the
developbranch has diverged from themasterbranch. - If a hot-fix needs to be applied, a new release may be cut at any time. If this happens, the release cycle does not change.
- Versions will be handled via GitHub Tags.
- Only
MAJORversions, as understood by the Semantic Versioning specification, are allowed; e.g.: increasing from version2.0.0to version3.0.0. - With each new version, the
composer.jsonfile must be updated to match the new target version before creating a tag. - After a new version is released,
magento-semverwill be packaged and published torepo.magento.comfor consumption.
vendor/bin/phpunit -c tests/Unit/phpunit.xml.dist