3 Release Checklist
There is no translation yet for this section. Please help out and translate this.. More information about translations
The following is a list of requirements that need to be satisfied when creating a release:
- Create a change log with clean, readable descriptions, referencing tickets wherever possible. See Git log parser, for a script to help generate change logs.
- Changes must be reflected in all written material prior to release.
- The code must be tested.
- The code should always be made available in the following archive formats: .zip, .tar.gz and .tar.bz2.
- Create a tag in git.
git tag -a -m '[message]' [version #] - Version numbers bumped:
- /cake/VERSION.txt
- /cake/config/config.php
- Website Updates:
- If the version is a minor/major release, make a new milestone in lighthouse.
- Download button updated
- Update any "special notices" (currently: Extra Hot ... at top of site)
- Cache cleared to ensure the above take effect.
- Post release announcement to the google group and bakery
- CakePHP Account to announce via Twitter


























