If you are about to implement a major feature, it is strongly recommended to get in touch with the developers. Such interaction will make it much more likely that your mods be applied to MantisBT distribution.
Patches should be attached to a Mantis Bug Tracker issue.
A patch should be attached as a single zip or .tar.gz file.
A patch should include a copy of all new files / modified files as well as a diff (patch) file (if possible).
A patch should only contain one feature. If a patch has a mixed bag of features, it makes it harder to understand and apply.
If you require feedback from developers relating to the patch, then post a message to mantisbt-dev at lists dot sourceforge dot net which refers to the issue including your patch. Ideally, the feedback will be added to the issue as notes. If not, then the patch owner should summarise the feedback as notes.
Fixes and updates to the patch should be attached to the same issue as should be marked clearly. With every attachment there should be a note that refers to the file name and specifies the updates done.
Join MantisBT IRC channel for realtime discussions with developers.
Patches should following MantisBT coding style.
Keep your patches up-to-date as new MantisBT versions are released.
