Maintainer Checklists

This page contains checklists CMF maintainers can/should follow when releasing new versions of their packages:

Package Release Checklist

Check the package milestone on GitHub and make sure the milestone is empty
Check the open issues and pull requests: There should be no important bugs pending for a fix
Add the version to the CHANGELOG file
Make sure minimum-stability is correctly set in composer.json (correctly means: RC when tagging an RC version, stable when tagging a stable version)
Check if the Travis config includes DEPS=low, DEPS=dev and all supported Symfony versions in between.
Run a complete Travis build from master and make sure it passes
Tag a signed release on the terminal: git tag -s 2.0.1 (without v prefix), Tag message: Released 2.0.1
Create a release on GitHub (go to the releases page, "Draft a new release" and create a release for the new tag)

When releasing a stable minor or major version, also do:

Create a new maintaince branch from master: git branch 2.0 origin/master
Update branch-alias in composer.json to the new dev version (e.g. 2.1) in the master branch

Make sure the application is in sync with the latest stable Symfony Standard Edition release.
Make sure minimum-stability is correctly set in composer.json (correctly means: RC when tagging an RC version, stable when tagging a stable version)
Check if the Travis config includes DEPS=low, DEPS=dev and all supported Symfony versions in between.
Run a complete Travis build from master and make sure it passes
Tag a signed release on the terminal: git tag -s 2.0.1 (without v prefix), Tag message: Released 2.0.1
Create a release on GitHub (go to the releases page, "Draft a new release" and create a release for the new tag)

Release CMF packages following Package Release Checklist in this order: (skip packages when no new release is needed)

After releasing all packages, release the Symfony CMF apps following the Application Release Checklist: