Release Process

Sebastian Bergmann edited this page Apr 4, 2016 · 17 revisions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Development

  • New features must be developed in feature branches
  • When a feature is ready, the respective feature branch will be merged to the master branch
  • Nightly builds from the master branch are available at https://phar.phpunit.de/phpunit-nightly.phar

Stable Release

  • PHPUnit follows Semantic Versioning 2.0.0
  • A new stable release (X.Y+1.0) is released every two months
  • Stable releases are available at https://phar.phpunit.de/phpunit-X.Y.Z.phar
  • The latest stable release is available at https://phar.phpunit.de/phpunit.phar

Support

A major release series such as 5.X MUST be supported for at least one year after the initial stable version (6.0.0) of the next major release series (6.0) is released.

The support for a minor release series such as 5.3 SHOULD end when a new minor version (such as 5.4.0) or a new major version (such as 6.0.0) is released.

PHP Version Requirement

A release series of PHPUnit that is actively supported MUST be compatible with all versions of PHP that are actively supported by the PHP project.

The minimum required version of PHP MAY only be bumped in a new major release of PHPUnit.