Submitting Patches to the vtiger Developer Community
This page decribes the format and procedure that code contributors should use to submit their patches to vtigercrm.
The short version is::
Create a unified diff against a subversion branch. Post the diff as a text attachment to a new or existing trac ticket which adequately describes your patch and its impact on the codebase.
Procedure for Submitting Patches
- Request trac access by sending mail to info at vtiger dot com
- Create a trac ticket for the bug. Use a full decription of the behavior, and full version information.
- Create a text file containing a unified diff against a subversion branch or subversion tag. Please only submit diffs against a subversion repository URL (e.g. a working copy), not an unpacked release archive. This will make it easier for the developers to merge your changes quickly and accurately.
- Attach the patch file to the trac ticket.
- Optionally, post a small description in the mailing list about the patch, but not containing the patch itself.
If you will be making frequent or large-scope code contributions, and are interested in becoming responsible developer in the vtiger community, you may wish to request subversion repository commit access, and develop your enhancements on a branch.
Windows related:
