Release Process

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.

Alpha (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 will be made available at https://phar.phpunit.de/phpunit-alpha.phar

Beta (Stabilization)

• A new release branch is created every two months
• Nightly builds from the current beta branch branch will be made available at https://phar.phpunit.de/phpunit-beta.phar

Stable Release

• PHPUnit follows Semantic Versioning 2.0.0
• A new stable release (X.Y+1.0) will be released after two months of stabilization
• Stable releases will be made available at https://phar.phpunit.de/phpunit-X.Y.Z.phar
• The latest stable release will be made available at https://phar.phpunit.de/phpunit.phar

Support

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

The support for a minor release series such as 4.0 SHOULD end when a new minor version (such as 4.1.0) or a new major version (such as 5.0.0) is released.