Release Process

This document describes the new release process for PHPUnit. It is still a work in progress. The new release process will be implemented beginning with PHPUnit 3.8.0, the next major release (the next release made from master).

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 as phpunit-alpha-YYYY-MM-DD.phar
• The latest nightly build from the master branch will be made available at 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 as phpunit-beta-YYYY-MM-DD.phar
• The latest nightly build from the current beta branch will be made available at 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 as phpunit-X.Y.Z.phar
• The latest stable release will be made available at phpunit.phar