Changes

Jump to: navigation, search

Bugzilla:Developers

230 bytes added, 21:14, 10 July 2007
no edit summary
4. Write some code. Make sure that you follow the [http://www.bugzilla.org/docs/developer.html Developer's Guide]. If you're new, you don't have to read the whole thing. Just read the [http://www.bugzilla.org/docs/developer.html#general General Guidelines], the [http://www.bugzilla.org/docs/developer.html#perl-style Style] section, and any other part that you think applies to the code that you're writing.
5. Test your patch. Make sure it works, and run ./runtests.pl in the Bugzilla directory. Also use [[Bugzillahttp:Patches|Make a patch]//validator.w3.org the HTML validator]to make sure your code generates valid HTML, if you modified any of Bugzilla's HTML.
6. [[Bugzilla:Submitting_PatchesPatches|Submit your Make a patch in Bugzilla]]
7. [[Bugzilla:ReviewSubmitting_Patches|Ask for reviewSubmit your patch in Bugzilla]]
78. Once your bug has passed [[Bugzilla:Review|Ask for review, the reviewer will ask for "approval". When approval is granted, you or the reviewer can commit the patch to CVS.]]
89. Once your bug has passed review, the reviewer will ask for "approval". When approval is granted, you or the reviewer can commit the patch to CVS. 10. [[Bugzilla:Committing_Patches|Commit your patch]], or get somebody else to commit it for you.
== Articles and Policies ==
Canmove, confirm
345
edits

Navigation menu