Submitting a Bug Fix

First, ensure you have the latest development version of the framework by checking out a copy from Subversion.

The easiest way to create a patch containing changes to multiple files, including new ones, is to add new files to your working copy. Then create the patch file using Subversion.

If you have commit permissions, be sure not to commit your fix back to the Subversion repository inadvertently. Only the component lead should commit changes to his or her component.

From the "trunk/" directory run the following command:

svn diff <dirname> \| tail \-n \+3 > <dirname>.diff

Then remove the changes:

svn revert \-R <dirname>

And patch from "trunk/":

patch \-p0 < <dirname>.diff

Finally, submit your patch (this means: attach the file containing your patch to the issue in the issuetracker). Thanks for helping us improve Zend Framework!

Patching a Release Version

Bug fix patches that will be submitted for community review should be made using the latest development version of the framework. However, some individual situations might require patches for a release version, such as when your customers are using an application you've developed based on Zend Framework.

To create a patch, first change your current directory to one directory above the library directory.

cd /path/to/Zend_Framework/library/..

Now make a new copy of the original release version into the directory "library.original", and execute the following command:

diff --exclude='*.original' --exclude='*~' --exclude='*.rej' --ignore-space-change -ruN library.original/ library/ > ZF-ver-x.x-my-changes.patch