Documentation Wiki

Submitting a patch

Submitting bugs is one the many contributions∞ that you can make to the PostNuke project. A patch that gets added for a future release can benefit the entire community.

Assembling the patch report

When submitting a patch assemble the following standard information

• The overview of the bug, issue or enhancement that this patch addresses
• Detailed technical information on what, how and why the patch does was it does
• The PostNuke version that this patch addresses
• Any test data or sample cases thart highlight the patch
• Any additional information that you think might help the developer evaluate the patch

If possible attempt to test the bug in a clean PostNuke insallation on as many server environments as possible.

Submitting the patch

To submit the patch you will need to have an account at the NOC. The user database is not synced with the main postnuke site so a seperate registration is required. Once you've got your NOC account you can submit a patch∞. On the submission form complete as many of the fields as you can and make sure to include all the information that you gathered earlier.

Feedback

Submission of a patch is the start of an interactive process where the developer that takes ownership of the patch may come back to you for additional information or more details on the information you've provided already so be prepared to assist the developer with further information should it be required.

Once the patch has been evaluated the patch the patch may be added to the codebase. It's important to note that not all patches will be added. A patch, while useful, may not be generic enough to be considered for the main codebase, a patch may not fit with the direction the development team want to take the codebase, a patch may be superceded by future devleopment etc.

Submitting more than one patch

If you have more than one patch please submit each patch seperately. This helps the development process as each patch may be assigned to a different developer.

---

CategoryKnowledgeBase